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 lemburg
Recipients eryksun, lemburg, methane, vstinner
Date 2021-03-19.15:02:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <d93d560b-58bb-ab92-3706-7905ba26138b@egenix.com>
In-reply-to <1616162249.48.0.772700997915.issue43552@roundup.psfhosted.org>
Content
On 19.03.2021 14:57, Inada Naoki wrote:
> 
> Background: PEP 597 adds new `encoding="locale"`option to open() and TextIOWrapper(). It is same to `encoding=None` for now, but it means using "locale encoding" explicitly.
> 
> But this is wrong in UTF-8 mode.

Please address UTF-8 mode explicitly in open() or elsewhere. The locale
module is about the state of the lib C, not what Python enforces via
options in its own I/O layers.

As mentioned, both should ideally be synchronized, though, so
UTF-8 mode in Python should trigger setting a UTF-8 encoding
via setlocale().
History
Date User Action Args
2021-03-19 15:02:41lemburgsetrecipients: + lemburg, vstinner, methane, eryksun
2021-03-19 15:02:41lemburglinkissue43552 messages
2021-03-19 15:02:41lemburgcreate