Message 338922 - Python tracker

➜

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	ncoghlan, vstinner
Date	2019-03-26.23:04:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1553641450.58.0.478845873462.issue36443@roundup.psfhosted.org>
In-reply-to

Content
bpo-36301 created a very strict separated between Python initialization and a new "pre-initialization" which is responsible to configure encodings and memory allocators. Nick Coghlan proposed to disable UTF-8 Mode and C locale coercion by default in the pre-initialization, so the LC_CTYPE locale is not coerced by Python when it's embedded in an application. Maybe the UTF-8 Mode can be automatically enabled (depending on the LC_CTYPE locale), but not the C locale coercion? This issue is related to bpo-36202: Calling Py_DecodeLocale() before _PyPreConfig_Write() can produce mojibake.

bpo-36301 created a very strict separated between Python initialization and a new "pre-initialization" which is responsible to configure encodings and memory allocators.

Nick Coghlan proposed to disable UTF-8 Mode and C locale coercion by default in the pre-initialization, so the LC_CTYPE locale is not coerced by Python when it's embedded in an application.

Maybe the UTF-8 Mode can be automatically enabled (depending on the LC_CTYPE locale), but not the C locale coercion?

This issue is related to bpo-36202: Calling Py_DecodeLocale() before _PyPreConfig_Write() can produce mojibake.

History
Date	User	Action	Args
2019-03-26 23:04:10	vstinner	set	recipients: + vstinner, ncoghlan
2019-03-26 23:04:10	vstinner	set	messageid: <1553641450.58.0.478845873462.issue36443@roundup.psfhosted.org>
2019-03-26 23:04:10	vstinner	link	issue36443 messages
2019-03-26 23:04:10	vstinner	create