2010/1/29 Antoine Pitrou <solip...@pitrou.net> > Cesare Di Mauro <cesare.di.mauro <at> gmail.com> writes: > > > > If python dev community is interested, I can work on a 3.x branch, > porting > > all optimizations I made (and many others that I've planned to implement) > one > > step at the time, in order to carefully check and validate any change > with > > expert people monitoring it. > > We are certainly more interested in a 3.x branch than in a 2.x one ;-) > You can start by cloning http://code.python.org/hg/branches/py3k/ > > Or you could submit patches piecewise on http://bugs.python.org
I prefer to make a branch with Mercurial, which I found a comfortable tool. :) > I think the first step would be to switch to 16-bit bytecodes. It would be > uncontroversial (the increase in code size probably has no negative effect) > and > would provide the foundation for all of your optimizations. > I agree. At the beginning I need to disable the peepholer, so performances are better to be compared when all peephole optimizations will be ported to the wordcode model. I'll make the branch after I release wpython 1.1, which I'll do ASAP. > Are you going to PyCon? > > Antoine. No, I don't. But if there's a python-dev meeting, I can make a (long) jump. May be it can be easier to talk about the superinstructions model, and I can show and comment all optimizations that I made. 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
