[docs] sys.getfilesystemencoding() changes for Python 3.3

Jed Ludlow jed.ludlow at gmail.com
Thu Apr 19 22:31:17 CEST 2012


The description of Unix behavior for sys.getfilesystemencoding() listed
here:

http://docs.python.org/dev/library/sys.html#sys.getfilesystemencoding

should probably change for Python 3.3. The behavior on Unix is the only
affected portion. According to the latest source at revision 293180d199f2
of the main hg repository, it is now a fatal error if the system call to
nl_langinfo(CODESET) fails to return a valid result, so Python does not
fall back to 'utf-8' encoding anymore. Instead, it aborts. In that light,
the bullet for Unix could now read:

   - On Unix, the encoding is the user’s preference according to the result
   of nl_langinfo(CODESET).

An applicable change note to replace the version 3.2 note would follow,
maybe:

Changed in version 3.3: On Unix, it is now a fatal error if
nl_langinfo(CODESET) fails to return a valid result during interpreter
initialization.
The relevant source commits are revision e2ba1249a2f5 and 7ce685cda0ae if
further verification is required.

Hope this helps.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120419/4a29b212/attachment.html>


More information about the docs mailing list