Brett Cannon added the comment: On Fri, Aug 31, 2012 at 6:42 PM, Antoine Pitrou <rep...@bugs.python.org>wrote:
> > Antoine Pitrou added the comment: > > > Might need to let Python 3 use its stdlib copy of lib2to3. Otherwise > > will need to come up with a way to have two copies of a library, one > > for Python 2 and another for Python 3, and then copy the right thing. > > Maybe a lib3 directory that is only copied over by make_perf3.sh? > > Sounds like a good idea. > Even better if you can find a 3.x copy of lib2to3 which is close the 2.x > one :-) > I think short of copying the stdlib versions from Python 2.7 and 3.2 I don't think there is much choice short of doing a 2to3+fixes translation ourselves just to have a version that is as close to the same as possible. But looking at the stdlib versions they are practically the same already except that one uses StringIO and the other uses io.StringIO (and Python 3 doesn't need the encode() call that triggered this whole discussion). I don't remember if StringIO or io.StringIO is faster in Python 2.6 and 2.7, but based on that we can either leave it as-is or tweak it to use the other just for benchmarking to make it even. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15834> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
