[Python-Dev] PEP 263 considered faulty (for some Japanese) (original) (raw)
Samuele Pedroni pedroni@inf.ethz.ch
Tue, 12 Mar 2002 21:39:48 +0100
- Previous message: [Python-Dev] PEP 263 considered faulty (for some Japanese)
- Next message: [Python-Dev] PEP 263 considered faulty (for some Japanese)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: Martin v. Loewis <martin@v.loewis.de>
Guido van Rossum <guido@python.org> writes:
> - file I/O; > > - OS filenames; > > - implicit mixing of 8-bit and Unicode strings; > > - invocation of unicode(s) or u.decode() without an encoding. I would not suggest to support a default encoding for file content. Instead, I think there should be a "terminal encoding", which is only used for interaction with the user's terminal.
In Jython we have such an encoding that can be set with the -E codec flag or a registry option (the moral equivalent of env var for CPython settings), at the moment AFAIK it is is only used for the interactive prompt input, whereas you presumably intented a default encoding for sys.stdin/out.
regards.
- Previous message: [Python-Dev] PEP 263 considered faulty (for some Japanese)
- Next message: [Python-Dev] PEP 263 considered faulty (for some Japanese)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]