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 ezio.melotti, ncoghlan, r.david.murray, vstinner
Date 2015-04-18.19:01:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hmm.  Upon reflection I guess I can see the validity of "if you are using the C locale you or the OS are broken anyway, so we'll just pass the bytes through".  I'm not entirely convinced this won't cause issues, but I suppose it might not cause any more issues that having things break due to the C locale does.

It is, however, going to return us to the days when a program that works fine most of the time suddenly blows up in the face of non-ascii data, and that's my biggest concern.

I'd certainly be fine with it if it wasn't the default (that is, programs who need this have to opt in to it).
Date User Action Args
2015-04-18 19:01:09r.david.murraysetrecipients: + r.david.murray, ncoghlan, vstinner, ezio.melotti
2015-04-18 19:01:09r.david.murraysetmessageid: <>
2015-04-18 19:01:09r.david.murraylinkissue23993 messages
2015-04-18 19:01:09r.david.murraycreate