➜

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 lemburg
Recipients Sworddragon, a.badger, bkabrda, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner
Date 2013-12-09.10:11:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386583915.11.0.38564520601.issue19846@psf.upfronthosting.co.za>
In-reply-to
Content 
The "C" locale is part of the ANSI C standard. The "POSIX" locale is an alias for the "C" locale and a POSIX standard, so we cannot just replace the ASCII encoding with UTF-8 as we wish, so Antoine's patch won't work.

See e.g. http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html

The C and POSIX locale settings are the only locale settings that are guaranteed to always exist in C libraries. Python 3 should work with such locale settings. It doesn't have to be able to output non-ASCII code points, but it should run with ASCII data.

AFAIK, Python 3 does work with ASCII data in the C locale, so I'm not sure whether this is a bug at all.
History
Date User Action Args
2013-12-09 10:11:55lemburgsetrecipients: + lemburg, loewis, terry.reedy, ncoghlan, pitrou, vstinner, larry, a.badger, r.david.murray, Sworddragon, serhiy.storchaka, bkabrda
2013-12-09 10:11:55lemburgsetmessageid: <1386583915.11.0.38564520601.issue19846@psf.upfronthosting.co.za>
2013-12-09 10:11:55lemburglinkissue19846 messages
2013-12-09 10:11:54lemburgcreate