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 akuchling
Recipients akuchling, georg.brandl, jlgijsbers, lemburg, loewis, meonkeys, mhammond, syvere, tim.peters
Date 2015-04-13.17:19:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428945559.04.0.455108767037.issue504219@psf.upfronthosting.co.za>
In-reply-to
Content
It doesn't seem to me that we've really deprecated getdefaultlocale() -- it's not documented as such, and MAL makes the good point that getdefaultlocale() is trying to avoid calling setlocale().

Perhaps this is just a documentation problem?  _build_localename() just glues together the language code and the encoding, resulting in things like en_US.ISO8859-1, which turns out to not work.  So maybe we should document that getdefaultlocale() will sometimes guess wrong.
History
Date User Action Args
2015-04-13 17:19:19akuchlingsetrecipients: + akuchling, lemburg, tim.peters, loewis, mhammond, georg.brandl, jlgijsbers, syvere, meonkeys
2015-04-13 17:19:19akuchlingsetmessageid: <1428945559.04.0.455108767037.issue504219@psf.upfronthosting.co.za>
2015-04-13 17:19:19akuchlinglinkissue504219 messages
2015-04-13 17:19:18akuchlingcreate