[Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale
Random832
random832 at fastmail.com
Tue Mar 14 15:06:53 EDT 2017
More information about the Python-Dev mailing list
Tue Mar 14 15:06:53 EDT 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 Tue, Mar 14, 2017, at 10:17, Nick Coghlan wrote: > It's not that you *can't* run Python 3 in that kind of environment, and > it's not that there are never any valid reasons to do so. It's that lots > of > things that you'd typically expect to work are going to misbehave (one I > discovered myself yesterday is that the GNU readline problems reported in > interactive mode on Android also show up when you do either "LANG=C > python2" or "LANG=C python3" on traditional Linux and attempt to *edit* > lines containing multi-byte characters) It occurs to me that (at least for readline... and maybe also as a general proxy for whether the rest should be done) detecting the IUTF8 terminal flag (which, properly, controls basic non-readline-based line editing such as backspace) may be worthwhile. (And maybe Readline itself should be doing this, more or less independent of Python. But that's a discussion for elsewhere)
- 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