bpo-29898: Fix incorrect env variable name (GH-1576)
It should read PYTHONLEGACYWINDOWSSTDIO as stated in section "Add legacy mode" in PEP 528.
This commit is contained in:
parent
1bd7d299bd
commit
87fa8a780e
|
@ -571,7 +571,7 @@ conflict.
|
|||
|
||||
.. versionchanged:: 3.6
|
||||
On Windows, the encoding specified by this variable is ignored for interactive
|
||||
console buffers unless :envvar:`PYTHONLEGACYWINDOWSIOENCODING` is also specified.
|
||||
console buffers unless :envvar:`PYTHONLEGACYWINDOWSSTDIO` is also specified.
|
||||
Files and pipes redirected through the standard streams are not affected.
|
||||
|
||||
.. envvar:: PYTHONNOUSERSITE
|
||||
|
@ -700,7 +700,7 @@ conflict.
|
|||
.. versionadded:: 3.6
|
||||
See :pep:`529` for more details.
|
||||
|
||||
.. envvar:: PYTHONLEGACYWINDOWSIOENCODING
|
||||
.. envvar:: PYTHONLEGACYWINDOWSSTDIO
|
||||
|
||||
If set to a non-empty string, does not use the new console reader and
|
||||
writer. This means that Unicode characters will be encoded according to
|
||||
|
|
|
@ -534,7 +534,7 @@ provide correctly read str objects to Python code. ``sys.stdin``,
|
|||
|
||||
This change only applies when using an interactive console, and not when
|
||||
redirecting files or pipes. To revert to the previous behaviour for interactive
|
||||
console use, set :envvar:`PYTHONLEGACYWINDOWSIOENCODING`.
|
||||
console use, set :envvar:`PYTHONLEGACYWINDOWSSTDIO`.
|
||||
|
||||
.. seealso::
|
||||
|
||||
|
|
Loading…
Reference in New Issue