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 r.david.murray
Recipients Anthony.Kong, berker.peksag, catalin.iacob, eric.araujo, petri.lehtinen, pitrou, poq, r.david.murray
Date 2012-02-20.02:13:31
SpamBayes Score 4.1226114e-05
Marked as misclassified No
Message-id <>
OK' I'm back to being 100% on the side of rejecting both of these changes.  ASCII is not unocode, it is bytes.  You can decode it to unicode but it is not unicode.  Those transformations operate bytes to bytes, not bytes to unicode.

We made the bytes unicode separation to avoid the problem where you have a working program that unexpectedly gets non ASCII input and blows up with a unicode error.  IMO these patches are reintroducing that problem.  The programer should have to explicitly encode to ASCII if they are inadvisedly workimg with it in a string as part of a wire protocol (why else would they be using these transforms).
Date User Action Args
2012-02-20 02:13:32r.david.murraysetrecipients: + r.david.murray, pitrou, eric.araujo, catalin.iacob, petri.lehtinen, poq, Anthony.Kong, berker.peksag
2012-02-20 02:13:32r.david.murraysetmessageid: <>
2012-02-20 02:13:31r.david.murraylinkissue13641 messages
2012-02-20 02:13:31r.david.murraycreate