➜

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 methane, vstinner
Date 2021-03-19.14:16:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1616163366.63.0.258541997283.issue43510@roundup.psfhosted.org>
In-reply-to
Content 
I replied to INADA-san message on bpo-43552:
https://bugs.python.org/issue43552#msg389091

> I had forgot to consider about UTF-8 mode while finishing PEP 597. If possible, I want to ignore UTF-8 mode when `encoding="locale"` is specified from Python 3.10.

In this case, the PEP 597 statement that open(filename, encoding="locale") is the same  than open(filename) is wrong. It would mean that users which got the UTF-8 Mode enabled (implicitly or explicitly) would switch to a legacy encoding like latin1 rather than using the UTF-8 encoding, if they add encoding="locale" to their open() calls?

Since the final goal is to move everybody towards to UTF-8, I'm not sure how it's a good thing.
History
Date User Action Args
2021-03-19 14:16:06vstinnersetrecipients: + vstinner, methane
2021-03-19 14:16:06vstinnersetmessageid: <1616163366.63.0.258541997283.issue43510@roundup.psfhosted.org>
2021-03-19 14:16:06vstinnerlinkissue43510 messages
2021-03-19 14:16:06vstinnercreate