2011/8/30 Antoine Pitrou <solip...@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
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
