On 2011-08-16, at 8:25 PM, Alex Gaynor wrote: > Personally I think #3 is the only sane path. We *need* a Python 2 VM for the > forseeable future. We're pretty lucky in that the JIT, GC, and all the > honest to god complex code is totally seperate from the VM, so just > supporting 2 Python VMs is kind of easy (compared to maintaing 2 JITs or > something).
Well, if everybody agrees on the 3rd option, then can we have at least the process of porting outlined and reviewed by core devs? No need for a super-detailed PEP, though. A simple guideline would help a lot. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
