➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients benjamin.peterson, eric.araujo, hfuru, loewis, vstinner
Date 2010-11-12.13:15:54
SpamBayes Score 0.0009694897
Marked as misclassified No
Message-id <1289567756.65.0.0739373793952.issue10070@psf.upfronthosting.co.za>
In-reply-to
Content 
I think 2to3 is designed to take 2.x code and turn it into 3.x code.  Codebases using tricks and hacks to support both 2.x and 3.x (like the example you linked to) cannot be handled by 2to3.  You have to make a choice between manual maintenance of parallel codebases, automatic 2to3 translation or cross-version compatibility.
History
Date User Action Args
2010-11-12 13:15:56eric.araujosetrecipients: + eric.araujo, loewis, hfuru, vstinner, benjamin.peterson
2010-11-12 13:15:56eric.araujosetmessageid: <1289567756.65.0.0739373793952.issue10070@psf.upfronthosting.co.za>
2010-11-12 13:15:54eric.araujolinkissue10070 messages
2010-11-12 13:15:54eric.araujocreate