Hi there, Armin:
> like what you would get if you imported in the same Python both the > "default" and the "py3k" branch (with the proper amount of import > hacks to keep them from conflicting). On Fri, Dec 9, 2011 at 4:50 PM, Amaury Forgeot d'Arc <[email protected]> wrote: > I was thinking of two object spaces with different config options, > like "config.objspace.std.py3k", > if we take the other route and have a single branch to support both > versions. 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? Regards, Martijn _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
