Albert-Jan Roskam wrote:
[me]
> Or you follow the convention and log to stderr:
>
> $ python3 -c 'import sys; print("\udc85", file=sys.stderr)'
> \udc85
> $ $ python3 -c 'import logging; logging.basicConfig();
> logging.getLogger().warn("\udc85")' > to_prove_it_s_not_stdout
> WARNING:root:\udc85
From: Tutor on behalf of
Peter Otten <__pete...@web.de>
Sent: Monday, September 25, 2017 2:59 PM
To: tutor@python.org
Subject: Re: [Tutor] logging to cmd.exe
Albert-Jan Roskam wrote:
> Hi,
>
>
> With Python 3.5 under Windows I am using the logging module to log
> messages to st
On Tue, Sep 26, 2017 at 7:35 AM, Mats Wichmann wrote:
> On 09/26/2017 05:22 AM, Albert-Jan Roskam wrote:
>
>> Rather than change your code can you change the codepage with the chcp
>> command?
>
> the way chcp takes effect is problematic for this:
>
> "Programs that you start after you assign a ne
> cmd.exe can use cp65001 aka utf8???
CMD is a Unicode application that for the most part uses WinAPI
wide-character functions, including the console API functions (as does
Python 3.6+). There are a few exceptions. CMD uses the console
codepage when decoding batch files (line by line, so you can c
On 09/26/2017 05:22 AM, Albert-Jan Roskam wrote:
> Rather than change your code can you change the codepage with the chcp
> command?
the way chcp takes effect is problematic for this:
"Programs that you start after you assign a new code page use the new
code page, however, programs (except Cmd.
From: Tutor on behalf of
Mark Lawrence via Tutor
Sent: Monday, September 25, 2017 4:19 PM
To: tutor@python.org
Subject: Re: [Tutor] logging to cmd.exe
On 25/09/2017 14:20, Albert-Jan Roskam wrote:
> Hi,
>
>
> With Python 3.5 under Windows I am using the logging module to log messages
> t
