[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-16 Thread Berker Peksag
Berker Peksag added the comment: New changeset 0d267041c40a3ab655676b885c0ba35ed9685848 by Berker Peksag in branch '3.6': bpo-29898: Fix incorrect env variable name (GH-1576) https://github.com/python/cpython/commit/0d267041c40a3ab655676b885c0ba35ed9685848 --

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-16 Thread Berker Peksag
Changes by Berker Peksag : -- resolution: -> fixed stage: backport needed -> resolved status: open -> closed ___ Python tracker

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-16 Thread Berker Peksag
Changes by Berker Peksag : -- pull_requests: +1700 ___ Python tracker ___ ___

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-16 Thread Berker Peksag
Changes by Berker Peksag : -- stage: test needed -> backport needed ___ Python tracker ___

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-16 Thread Berker Peksag
Berker Peksag added the comment: New changeset 87fa8a780e9045a26c735f085c07bba4b2d0be60 by Berker Peksag in branch 'master': bpo-29898: Fix incorrect env variable name (GH-1576) https://github.com/python/cpython/commit/87fa8a780e9045a26c735f085c07bba4b2d0be60 -- nosy: +berker.peksag

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-05-13 Thread Berker Peksag
Changes by Berker Peksag : -- pull_requests: +1669 ___ Python tracker ___ ___

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-03-25 Thread Steve Dower
Steve Dower added the comment: Sure, but you're proposing a change to a correctly documented (apart from the variable name) and released behavior. It can't be changed in 3.6, and I don't see a compelling reason to have different behavior in 3.7. --

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-03-25 Thread Eryk Sun
Eryk Sun added the comment: I prefer the name PYTHONLEGACYWINDOWSIOENCODING for symmetry with both PYTHONIOENCODING and PYTHONLEGACYWINDOWSFSENCODING, but I suppose you changed it to make it more visually distinguished from the latter. I discovered this issue due to the modified behavior of

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-03-24 Thread Steve Dower
Steve Dower added the comment: It's actually called "PYTHONLEGACYWINDOWSSTDIO" in Python/pylifecycle.c, which is also what PEP 528 says it should be, so this is a docs issue. You're correct that PYTHONIOENCODING is overridden by detection of a real console, however, PYTHONIOENCODING doesn't

[issue29898] PYTHONLEGACYWINDOWSIOENCODING isn't implemented

2017-03-24 Thread Eryk Sun
New submission from Eryk Sun: The environment variable PYTHONLEGACYWINDOWSIOENCODING is documented here: https://docs.python.org/3/using/cmdline.html#envvar-PYTHONLEGACYWINDOWSIOENCODING but not actually implemented. Also, I think setting PYTHONIOENCODING to anything except UTF-8 should