Rob Williscroft wrote:
AIUI the idea is that you write your 2.x python code (and tests) so
that when they are processed by 2to3.py you get valid python 3.x
code that will pass all its tests.
You then maintain your 2.x code base adding another test where the
code (and tests) is run through 2to3.py and then python 3.x runs
the test suite.
Presumably you only need to start maintining a 3.x code base when
you start adding 3.x specific features or abandon support for
2.x python.
http://wiki.python.org/moin/Early2to3Migrations
reports some early experiences (some a year old). Martin's was edited
most recently, but even his report misses recent changes to 2to3.
--
http://mail.python.org/mailman/listinfo/python-list
