[Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces (original) (raw)
Simon Cross hodgestar+pythondev at gmail.com
Fri Apr 24 11:37:02 CEST 2009
- Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
- Next message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Apr 24, 2009 at 11:22 AM, Glenn Linderman <v+python at g.nevcal.com> wrote:
Oh clearly it is a hack. The right solution of a Path type (and friends) was discarded in earlier discussion, because it would impact too much existing code. The use of bytes would be annoying in the context of py3, where things that you want to display are in str (Unicode). So there is no solution that allows the use of str, and the robustness of bytes, and is 100% compatible with existing practice. Hence the desire is to find a hack that is "good enough". At least, that is my understanding and synopsis.
What about keeping the bytes interface (utf-8 encoded Unicode on Windows) and adding a Path type (and friends) interface that mirrors it?
(Sorry Simon, but it is still the same thread, anyway.)
Python discussions do seem to womble through a rather large set of mailing lists and news groups. :)
Schiavo Simon
- Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
- Next message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]