➜
See More

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 vstinner
Recipients vstinner
Date 2010-05-04.23:34:24
SpamBayes Score 3.1344393e-07
Marked as misclassified No
Message-id <[email protected]>
In-reply-to
Content 
Here is a patch for the first solution: display a fatal error if we are unable to get the locale encoding. It does always exit with a fatal error if nl_langinfo(CODESET) is not available (and Py_FileSystemDefaultEncoding is not set).

I don't think it's a good idea to display an fatal error at runtime. If nl_langinfo(CODESET) is not available, configure should fail or we should fallback to an hardcoded encoding (ok but which one?).

Extract of the nl_langinfo() manual page (on Linux):

CONFORMING TO
       SUSv2, POSIX.1-2001.
History
Date User Action Args
2010-05-04 23:34:28vstinnersetrecipients: + vstinner
2010-05-04 23:34:27vstinnersetmessageid: <[email protected]>
2010-05-04 23:34:25vstinnerlinkissue8610 messages
2010-05-04 23:34:25vstinnercreate