A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-March/021010.html below:

[Python-Dev] PEP 263 considered faulty (for some Japanese)

[Python-Dev] PEP 263 considered faulty (for some Japanese) [Python-Dev] PEP 263 considered faulty (for some Japanese)Samuele Pedroni pedroni@inf.ethz.ch
Tue, 12 Mar 2002 21:39:48 +0100
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.




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4