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 loewis
Recipients Sworddragon, ezio.melotti, lemburg, loewis, ncoghlan, r.david.murray, serhiy.storchaka, vstinner
Date 2014-06-22.20:35:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403469308.58.0.498907103679.issue21331@psf.upfronthosting.co.za>
In-reply-to
Content
As you say, the unicode-escape codec is tied to the Python language definition. So if the language changes, the codec needs to change as well. 

A Unicode literal in source code might be using any encoding, so to be on the safe side, restricting it to ASCII is meaningful. Or else, if we want to use the default source encoding (as it did in 2.x), we should assume UTF-8 (per PEP 3120). Using ISO-8859-1 is clearly wrong for 3.x.
History
Date User Action Args
2014-06-22 20:35:08loewissetrecipients: + loewis, lemburg, ncoghlan, vstinner, ezio.melotti, r.david.murray, Sworddragon, serhiy.storchaka
2014-06-22 20:35:08loewissetmessageid: <1403469308.58.0.498907103679.issue21331@psf.upfronthosting.co.za>
2014-06-22 20:35:08loewislinkissue21331 messages
2014-06-22 20:35:08loewiscreate