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 benjamin.peterson
Recipients Arfrever, benjamin.peterson, lemburg, loewis, serhiy.storchaka
Date 2017-03-11.07:55:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489218904.01.0.0364266302295.issue20087@psf.upfronthosting.co.za>
In-reply-to
Content
I'm still confused about what getlocale() is supposed to do. Why do we attempt to return an encoding anyway if the underlying setlocale call doesn't return one? Is getlocale() not supposed to a simple wrapper over the C locale? If not, how is one supposed to get the encoding associated with the C locale?

The old alias table code meant that the encoding returned from getlocale() could be related to or completely unrelated to the actual C locale. Misunderstanding this results in issues like #29571.
History
Date User Action Args
2017-03-11 07:55:04benjamin.petersonsetrecipients: + benjamin.peterson, lemburg, loewis, Arfrever, serhiy.storchaka
2017-03-11 07:55:04benjamin.petersonsetmessageid: <1489218904.01.0.0364266302295.issue20087@psf.upfronthosting.co.za>
2017-03-11 07:55:04benjamin.petersonlinkissue20087 messages
2017-03-11 07:55:03benjamin.petersoncreate