Message104984
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. |
|
Date |
User |
Action |
Args |
2010-05-04 23:34:28 | vstinner | set | recipients:
+ vstinner |
2010-05-04 23:34:27 | vstinner | set | messageid: <1273016067.99.0.713871493039.issue8610@psf.upfronthosting.co.za> |
2010-05-04 23:34:25 | vstinner | link | issue8610 messages |
2010-05-04 23:34:25 | vstinner | create | |
|