On Wed, Jul 16, 2008 at 5:21 AM, Michael Foord <[EMAIL PROTECTED]> wrote: > Terry Reedy wrote: >> >> >> Michael Foord wrote: >>> >>> Collin Winter wrote: >> >>>> Is any provision being made for a 2to3 fixer/otherwise-automated >>>> transition for the changes you propose here? >>>> >>> >>> As the deprecation is intended for 2.X and 3.X - is 2to3 fixer needed? >> >> A fixer will only be needed when it actually is needed, but when it is, it >> should be a unittest-name fixer since previous 3.x code will also need >> fixing. Since the duplicates are multiples names for the same objects, the >> fixer should be a trivial name substitution. > > Can 2to3 fixers be used for 2to2 and 3to3 translation then?
The intention is for the infrastructure behind 2to3 to be generally reusable for other Python source-to-source translation tools, be that 2to2 or 3to3. That hasn't fully materialized yet, but it's getting there. Collin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
