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 ncoghlan
Recipients Sworddragon, a.badger, bkabrda, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner
Date 2013-12-13.12:51:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7cfXHR+iKYPyPB70oBTc2h33SW6pB-UvtmJ5iiq4Yf=aw@mail.gmail.com>
In-reply-to <1386937189.81.0.736900543235.issue19846@psf.upfronthosting.co.za>
Content
There's an alternative to trying to force a different encoding for the
standard streams when the OS claims ASCII as the OS encoding: we can
default to surrogateescape as the error handler, on the assumption that
whatever the *real* OS encoding is, it definitely isn't ASCII.

That means we'll still complain about displaying improperly encoded data
when the OS suggests a plausible encoding, but we won't fail entirely just
because someone enabled (deliberately or accidentally) the POSIX locale.
History
Date User Action Args
2013-12-13 12:51:39ncoghlansetrecipients: + ncoghlan, lemburg, loewis, terry.reedy, pitrou, vstinner, larry, a.badger, r.david.murray, Sworddragon, serhiy.storchaka, bkabrda
2013-12-13 12:51:39ncoghlanlinkissue19846 messages
2013-12-13 12:51:39ncoghlancreate