PYTHONIOENCODING is ignored (at least on Windows)

[lv-gh]

Is this normal behavior (couldn't find any clarifications on that)?

ipython -c "import sys, os; print(os.environ['PYTHONIOENCODING']); print(sys.stdin.encoding); print(sys.stdout.encoding);"
ISO-8859-13
utf-8
utf-8

versus:

python -c "import sys, os; print(os.environ['PYTHONIOENCODING']); print(sys.stdin.encoding); print(sys.stdout.encoding);"
ISO-8859-13
ISO-8859-13
ISO-8859-13

[minrk]

What Python and IPython version? This is what I would expect in a notebook, where we define utf8 for the transport, but terminal IPython probably shouldn't behave differently.

@takluyver?

[lv-gh]

@minrk
Sorry.

C:\Python64\3.5>python.exe -V
Python 3.5.2

ipython -V
C:\Python64\3.5>ipython -V
5.1.0

[takluyver]

I guess our encoding detection incorrectly takes priority over the environment variable. It shouldn't have a big effect, though, because now that we use win_unicode_console, unicode is written to the terminal with the unicode APIs, not encoded.

[takluyver]

On thinking about this a bit more, it's due to our use of win_unicode_console. We've effectively backported a change from Python 3.6. On 3.6 on Windows, PYTHONIOENCODING is ignored in a console unless PYTHONLEGACYWINDOWSIOENCODING is also set. Possibly we should add support for that environment variable to disable prompt_toolkit. I'll leave this issue open as a feature request for that, but mark it wishlist.

On Linux, setting PYTHONIOENCODING works as expected:

$ PYTHONIOENCODING=ISO-8859-13 ipython -c "import sys; print(sys.stdin.encoding)"
ISO-8859-13
$ PYTHONIOENCODING=ISO-8859-13 ipython -c "import sys; print(sys.stdout.encoding)"
ISO-8859-13

[SLAYER-CODE]

Solo reinicie la terminal y se arreglo momentos despues de crear el entorno virtual y visualisar el fallo