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 lregebro
Recipients georg.brandl, lregebro
Date 2008-12-06.09:55:16
SpamBayes Score 1.6843682e-09
Marked as misclassified No
Message-id <1228557320.05.0.356460400816.issue4559@psf.upfronthosting.co.za>
In-reply-to
Content
The whatsnew/3.0.rst document claims

"It is not recommended to try to write source code that runs unchanged
under both Python 2.6 and 3.0; you’d have to use a very contorted coding
style, e.g. avoiding print statements, metaclasses, and much more. "

This is no longer true, since 2.6 now has much backwards compatibility,
including fopr print statements and unicode, so it's prefectly possible
and not at all contorted to support both any longer.

I'd recommend that the above statement is changed to "under both Python
2.5 and 3.0" or simply removed.
History
Date User Action Args
2008-12-06 09:55:21lregebrosetrecipients: + lregebro, georg.brandl
2008-12-06 09:55:20lregebrosetmessageid: <1228557320.05.0.356460400816.issue4559@psf.upfronthosting.co.za>
2008-12-06 09:55:18lregebrolinkissue4559 messages
2008-12-06 09:55:17lregebrocreate