➜

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 koobs, ncoghlan, vstinner
Date 2018-11-23.11:27:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542972449.24.0.788709270274.issue35290@psf.upfronthosting.co.za>
In-reply-to
Content 
Ok, I found the bug: it is related to the commit 905f1ace5f7424e314ca7bed997868a2a3044839 of bpo-34523. Python now uses ASCII for the filesystem encoding if the internal "force ASCII" mode is enabled in Py_DecodeLocale/Py_EncodeLocale.

FreeBSD CURRENT introduced a new C.UTF-8 locale which is used by C locale coercion (PEP 538).

_PyCoreConfig_Read() now uses ASCII for the filesystem encoding if the "force ASCII" mode is enable (to ensure that encodings are consistent everywhere Python).

Problem: The LC_CTYPE now uses UTF-8 (thanks to C locale coercion) whereas Python uses ASCII for the filesystem encoding since the "force ASCII" is still enabled.

I wrote PR 10672 to reset the "force ASCII" mode. I tested manually my fix on the FreeBSD CURRENT buildbot.
History
Date User Action Args
2018-11-23 11:27:29vstinnersetrecipients: + vstinner, ncoghlan, koobs
2018-11-23 11:27:29vstinnersetmessageid: <1542972449.24.0.788709270274.issue35290@psf.upfronthosting.co.za>
2018-11-23 11:27:29vstinnerlinkissue35290 messages
2018-11-23 11:27:29vstinnercreate