On 4/27/06, Ron Adam <[EMAIL PROTECTED]> wrote: > I think it's been suggested before that there should be a PY2.x to PY3.x > conversion utility to facilitate the move to PY3K. So maybe a sticking > point as when to *not* do something would be, if it's not possible to > translate a changed 2.x feature to a PY3K equivalent automatically > rather than if it will break 2.x code or not.
Please read the section "Compatibility and Transition" in PEP 3000. Perfect automatic translation is not a goal. A combination of tools should be able to diagnose all areas of a program that require changes but may not necessarily be able to tell you how to change it. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
