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 brett.cannon
Recipients brett.cannon, lemburg, loewis, meatballhat, pitrou, vstinner
Date 2010-05-25.21:43:26
SpamBayes Score 0.0282609
Marked as misclassified No
Message-id <>
That deprecation is way too fast. If someone wants to write code that works in Python 2.5 or older *and* Python 3 then will most likely be how they keep compatibility for reading in encoded files.

But yes, overall it should get deprecated. Probably a PendingDeprecationWarning to start is good and then eventually switch to a DeprecationWarning once most Linux distributions have moved to Python 2.6.
Date User Action Args
2010-05-25 21:43:30brett.cannonsetrecipients: + brett.cannon, lemburg, loewis, pitrou, vstinner, meatballhat
2010-05-25 21:43:29brett.cannonsetmessageid: <>
2010-05-25 21:43:27brett.cannonlinkissue8796 messages
2010-05-25 21:43:27brett.cannoncreate