On 13 October 2011 19:55, Antonio Cuni <anto.c...@gmail.com> wrote: > - support for py2 and py3 in the same branch, with minimal duplication of > code. This would mean that e.g. in ast.py you would have tons of "if py2: > enable_print_stmt()", etc. Personally, I think that the codebase would > become too cluttered.
In order to support __future__.print_function, you already need this case. Do we have a good idea of where we expect the biggest divergence? Is it things that now return iterables or views, or is it IO? Is it new-style defaults, or unicode field names? > - support for py2 and py3 in the same branch, with some duplication of code; > e.g., we could copy the existing interpreter/ into interpreter/py3k and > modify it there. While we are at it, we should try hard to minimize the > code duplication, but then it's up to us to decide when it's better to > duplicate or when it's better to share the code between the twos. An adaptive approach sounds very sensible. -- William Leslie _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev