[Python-Dev] Python 3 optimizations continued...

"Martin v. Löwis" martin at v.loewis.de
Tue Aug 30 10:40:16 CEST 2011


>> Although any such patch should discuss how it compares with Cesare's
>> work on wpython.
>> Personally, I *like* CPython fitting into the "simple-and-portable"
>> niche in the Python interpreter space.
> 
> Changing the bytecode width wouldn't make the interpreter more complex.

No, but I think Stefan is proposing to add a *second* byte code format,
in addition to the one that remains there. That would certainly be an
increase in complexity.

> Some years ago we were waiting for Unladen Swallow to improve itself
> and be ported to Python 3. Now it seems we are waiting for PyPy to be
> ported to Python 3. I'm not sure how "let's just wait" is a good
> trade-off if someone proposes interesting patches (which, of course,
> remains to be seen).

I completely agree. Let's not put unmet preconditions to such projects.

For example, I still plan to write a JIT for Python at some point. This
may happen in two months, or in two years. I wouldn't try to stop
anybody from contributing improvements that may become obsolete with the
JIT. The only recent case where I *did* try to stop people is with
PEP-393, where I do believe that some of the changes that had been
made over the last year become redundant.

Regards,
Martin


More information about the Python-Dev mailing list