Message290467
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 PYTHONIOENCODING. It's not really a disruptive change, but it looks wrong based solely on the --help text description of PYTHONIOENCODING. An alternative would be to set Py_LegacyWindowsStdioFlag in _Py_InitializeEx_Private either when PYTHONLEGACYWINDOWSSTDIO is set or when PYTHONIOENCODING isn't a case-insensitive match for "utf-8" with an optional :errors spec. That way people get exactly what they asked for, even if it's mojibake nonsense given the console's current input and output codepages. |
|
Date |
User |
Action |
Args |
2017-03-25 07:42:54 | eryksun | set | recipients:
+ eryksun, paul.moore, vstinner, tim.golden, ezio.melotti, docs@python, zach.ware, steve.dower |
2017-03-25 07:42:54 | eryksun | set | messageid: <1490427774.11.0.442994010342.issue29898@psf.upfronthosting.co.za> |
2017-03-25 07:42:54 | eryksun | link | issue29898 messages |
2017-03-25 07:42:54 | eryksun | create | |
|