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 amcnabb
Recipients amcnabb, ezio.melotti, georg.brandl, loewis
Date 2010-03-12.21:22:59
SpamBayes Score 3.263808e-05
Marked as misclassified No
Message-id <1268428981.38.0.771098079453.issue8127@psf.upfronthosting.co.za>
In-reply-to
Content
By the way, I just noticed your notes on the wiki page and added a response/question.  It seems that the advice that you consider bad is the official porting story (upgrade to 2.6 and use 2to3).  I agree that it's easier and better to not drop support for 2.4 and 2.5, but this seems to be officially discouraged.  The current content on the What's New page only talks about upgrading to 2.6 and using 2to3.

In any case, most of the current content on the wiki page is about supporting Python 2 and Python 3 simultaneously.  I think this is actually better than the official documentation.
History
Date User Action Args
2010-03-12 21:23:01amcnabbsetrecipients: + amcnabb, loewis, georg.brandl, ezio.melotti
2010-03-12 21:23:01amcnabbsetmessageid: <1268428981.38.0.771098079453.issue8127@psf.upfronthosting.co.za>
2010-03-12 21:22:59amcnabblinkissue8127 messages
2010-03-12 21:22:59amcnabbcreate