[Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
Guido van Rossum
guido at python.org
Wed Mar 8 16:58:29 EST 2017
More information about the Python-Dev mailing list
Wed Mar 8 16:58:29 EST 2017
- Previous message (by thread): [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
- Next message (by thread): [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Mar 8, 2017 at 4:35 AM, Nick Coghlan <ncoghlan at gmail.com> wrote: > > On 5 March 2017 at 17:50, Nick Coghlan <ncoghlan at gmail.com> wrote: > >> Late last year I started working on a change to the CPython CLI (*not* >> the shared library) to get it to coerce the legacy C locale to something >> based on UTF-8 when a suitable locale is available. >> >> After a couple of rounds of iteration on linux-sig and python-ideas, I'm >> now bringing it to python-dev as a concrete proposal for Python 3.7. >> > > In terms of resolving this PEP, if Guido doesn't feel inclined to wade > into the intricacies of legacy C locale handling, Barry has indicated he'd > be happy to act as BDFL-Delegate :) > Hi Nick and Barry, I'd very much appreciate if you two could resolve this without involving me. Godspeed! -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170308/823fa947/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
- Next message (by thread): [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list