[Python-Dev] Python 3 optimizations continued... (original) (raw)

Cesare Di Mauro cesare.di.mauro at gmail.com
Wed Aug 31 07:04:35 CEST 2011

2011/8/30 Antoine Pitrou <solipsis at pitrou.net>

Changing the bytecode width wouldn't make the interpreter more complex.

It depends on the kind of changes. :)

WPython introduced a very different "intermediate code" representation that required a big change on the peepholer optimizer on 1.0 alpha version. On 1.1 final I decided to completely move that code on ast.c (mostly for constant-folding) and compiler.c (for the usual peepholer usage: seeking for some "patterns" to substitute with better ones) because I found it simpler and more convenient.

In the end, taking out some new optimizations that I've implemented "on the road", the interpreter code is a bit more complex.

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). Regards Antoine. It isn't, because motivation to do something new with CPython vanishes, at least on some areas (virtual machine / ceval.c), even having some ideas to experiment with. That's why in my last talk on EuroPython I decided to move on other areas (Python objects).

Regards

Cesare -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110831/a99b7f7d/attachment-0001.html>

More information about the Python-Dev mailing list