Re: Changing the (codec) error handler for the stdout/stderr streamsin Python 3.0

[John Nagle]

Jukka Aho wrote:

Just a tip for those who are only just cutting their teeth on Python 3.0
and might have encountered the same problem as I did:
>
When a Python (3.x) program is run on a terminal that only supports a
legacy character encoding - such as Latin 1 or Codepage 437 - all
characters printed to stdout will be automatically converted from the
interpreter's internal Unicode representation to this legacy character set.

Python 5 is even stricter. Only ASCII (chars 0..127) can be sent
to standard output by default.

John Nagle

[Steven D'Aprano]

Re: Changing the (codec) error handler for the stdout/stderrstreams in Python 3.0

On Tue, 02 Sep 2008 09:57:05 -0700, John Nagle wrote:

Jukka Aho wrote:

>Just a tip for those who are only just cutting their teeth on Python
>3.0 and might have encountered the same problem as I did:
>>
>When a Python (3.x) program is run on a terminal that only supports a
>legacy character encoding - such as Latin 1 or Codepage 437 - all
>characters printed to stdout will be automatically converted from the
>interpreter' s internal Unicode representation to this legacy character
>set.

>
Python 5 is even stricter. Only ASCII (chars 0..127) can be sent
to standard output by default.

Python 5??? Is this the time machine again?



--
Steven

[Jukka Aho]

Re: Changing the (codec) error handler for the stdout/stderr streams in Python 3.0

John Nagle wrote:

Python 5 is even stricter. Only ASCII (chars 0..127) can be sent
to standard output by default.

Python 5? (I guess I haven't been following these things enough...)

Well, I would sure hope not.

--
znark