On 09:37 pm, tjreedy@udel.edu wrote:
On 12/13/2011 10:54 AM, Vinay Sajip wrote:
I started writing a tool today, tentatively called '2to23', which aims to do this. It's basically 2to3, but with a package of custom fixers in a package 'lib2to23.fixers' adapted from the corresponding fixers in lib2to3.
When, some year in the future, people want to drop Python 2 compatibility from their Python23 code, they will need a 23to3 tool.
No, they will not. They only need a 2to3 or 2to6 tool because Python 2 and Python 3 are not compatible with each other, but they want one program to be valid in Python 2 and Python 3 simultaneously. When they decide they no longer care about Python 2, they can just stop taking care to keep their program valid as Python 2 and only take care to keep it a valid Python 3 program. There's no specific change to make, just a different approach to take with future maintenance. You might say that they will *want* to immediately discard all of their legacy Python 2 support code. I suspect many of them will not want this; but either way it's a want, not a need. Jean-Paul