Hey, On Fri, Dec 9, 2011 at 6:27 PM, Armin Rigo <[email protected]> wrote: > On Fri, Dec 9, 2011 at 17:57, Martijn Faassen <[email protected]> wrote: >> Oh, I was assuming that PyPy would have one branch supporting both >> python 2 and python 3. Is that currently not the case? What are the >> reasons behind not separating the two implementations in different >> packages? > > I think it was not deeply thought out, but was just the simplest route > to take. It does give us (mostly for free) a feature that is > completely essential to have: continuously merging the "default" > changes in "py3k". Otherwise it would be a mess that would end up > with py3k not including all the more recent Python fixes and > performance improvements we keep doing.
Yes, I figured merging would be the main benefit, that makes sense. Hopefully it can be made to work in parallel with the Python 2 implementation eventually though. Regards, Martijn _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
