Raymond Hettinger raymond.hettinger at gmail.com
Thu May 28 14:46:56 CEST 2015

• Previous message (by thread): [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)
• Next message (by thread): [Python-Dev] Computed Goto dispatch for Python 2
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> On May 28, 2015, at 1:54 AM, Berker Peksağ <berker.peksag at gmail.com> wrote:
> 
> * Performance improvements are not bug fixes

Practicality beats purity here.   
Recognize that a huge number of Python users will remain in the Python2.7 world
for some time.  We have a responsibility to the bulk of our users (my estimate is
that adoption rate for Python 3 is under 2%).  The computed goto patch makes
substantial performance improvements.  It is callous to deny the improvement
to 2.7 users.


> * The patch doesn't make the migration process from Python 2 to Python 3 easier

Sorry, that is a red-herring (an orthogonal issue).
If you care about 2-to-3 migration, then start
opposing proposals for API changes that increase
the semantic difference between 2 and 3.



Raymond

---

• Previous message (by thread): [Python-Dev] Keeping competitive with Go (was Re: Computed Goto dispatch for Python 2)
• Next message (by thread): [Python-Dev] Computed Goto dispatch for Python 2
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list