This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients ezio.melotti, jaraco, lemburg, loewis, vstinner
Date 2014-07-11.16:15:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405095306.74.0.191708344513.issue21927@psf.upfronthosting.co.za>
In-reply-to
Content
I get different results that @haypo when testing Powershell on Windows 8.1 with Python 3.4.1:

C:\Users\jaraco> chcp 1252
Active code page: 1252
C:\Users\jaraco> $env:PYTHONIOENCODING=''
> How you do change the console encoding? Using the chcp command?

Yes. I recently discovered that if I use chcp 65001 in my Powershell profile, I can finally see Unicode characters output from my Python programs!

> I'm surprised that you get a UTF-8 BOM when the code page 1252 is used. Can you please check that sys.stdin.encoding is "cp1252"?

C:\Users\jaraco> echo foo | python -c "import sys; print(sys.stdin.readline())"
foo

C:\Users\jaraco> python -c "import sys; print(sys.stdin.encoding)"
cp1252

C:\Users\jaraco> chcp 65001

C:\Users\jaraco> echo foo | python -c "import locale, os; print(os.device_encoding(0), locale.getpreferredencoding(False))"
None cp1252

It seems as if something may have changed in Powershell between Windows 7 and 8.1, because my results are inconsistent with your findings.

There's a lot more to digest from your response, so I'll going to have to revisit this later.
History
Date User Action Args
2014-07-11 16:15:06jaracosetrecipients: + jaraco, lemburg, loewis, vstinner, ezio.melotti
2014-07-11 16:15:06jaracosetmessageid: <1405095306.74.0.191708344513.issue21927@psf.upfronthosting.co.za>
2014-07-11 16:15:06jaracolinkissue21927 messages
2014-07-11 16:15:06jaracocreate