[Python-Dev] PEP 540: Add a new UTF-8 mode (v3)
Victor Stinner
victor.stinner at gmail.com
Sun Dec 10 04:57:32 EST 2017
More information about the Python-Dev mailing list
Sun Dec 10 04:57:32 EST 2017
- Previous message (by thread): [Python-Dev] PEP 540: Add a new UTF-8 mode (v3)
- Next message (by thread): [Python-Dev] PEP 540: Add a new UTF-8 mode (v3)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, Le 10 déc. 2017 05:48, "INADA Naoki" <songofacandy at gmail.com> a écrit : Now I'm OK to accept the PEP, except one nitpick. I got a private email about the same issue. I don't think that it's nitpicking since many people were confused about the relationship between the PEP 538 and PEP 540. So it seems like I was confused as well :-) I was also confused because my PEP evolved quickly. With the additionnal local.getpreferredenconding() change in my PEP, the two PEP became even more similar. > Locale coercion only impacts non-Python code like C libraries, whereas > the Python UTF-8 Mode only impacts Python code: the two PEPs are > complementary. > This sentence seems bit misleading. If UTF-8 mode is disabled explicitly, locale coercion affects Python code too. locale.getpreferredencoding() is UTF-8, open()' s default encoding is UTF-8, and stdio is UTF-8/surrogateescape. So shouldn't this sentence is: "Locale coercion impacts both of Python code and non-Python code like C libraries, whereas ..."? Right. I will rephrase it. Victor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171210/9d978ed0/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 540: Add a new UTF-8 mode (v3)
- Next message (by thread): [Python-Dev] PEP 540: Add a new UTF-8 mode (v3)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list