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 eryksun, iritkatriel, ncoghlan, r.david.murray, sejvlond, vstinner
Date 2021-08-30.15:31:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630337469.61.0.83053285862.issue25867@roundup.psfhosted.org>
In-reply-to
Content
> It's doing this now, so seems like it has been fixed: % env -i ./python.exe (...)

Right. It's correct to close the issue.

The PEP 540 added a UTF-8 Mode. This mode is enabled if Python is started with the "C" or "POSIX" locale (LC_CTYPE category). If the UTF-8 Mode is enabled, Python uses UTF-8 for its "filesystem" encoding:

* https://docs.python.org/dev/library/os.html#python-utf-8-mode
* https://docs.python.org/dev/glossary.html#term-filesystem-encoding-and-error-handler

Moreover, the PEP 538 also tries to use a UTF-8 variable of "C" and "POSIX" locales, which also fix this issue.

I documented how Python configures its "filesystem encoding" at:
https://docs.python.org/dev/c-api/init_config.html#c.PyConfig.filesystem_encoding
History
Date User Action Args
2021-08-30 15:31:09vstinnersetrecipients: + vstinner, ncoghlan, r.david.murray, eryksun, sejvlond, iritkatriel
2021-08-30 15:31:09vstinnersetmessageid: <1630337469.61.0.83053285862.issue25867@roundup.psfhosted.org>
2021-08-30 15:31:09vstinnerlinkissue25867 messages
2021-08-30 15:31:09vstinnercreate