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 eryksun
Recipients eryksun, twoone3
Date 2020-10-05.09:47:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601891276.99.0.544135252286.issue41941@roundup.psfhosted.org>
In-reply-to
Content
Python supports Unicode in a Windows console session by using the console API's wide-character functions (i.e. ReadConsoleW and WriteConsoleW) with UTF-16 encoded text. This is implemented in the io stack via io._WindowsConsoleIO, and for PyOS_Readline (e.g. builtin `input`) via _PyOS_WindowsConsoleReadline. The UTF-16 aspect is an internal detail that's presented externally as UTF-8 by automatically converting between the two.

Notwithstanding the behavior of third-party packages, CPython intentionally makes no changes to a console session's global settings, including:

    * input & output codepages
    * input & output modes (except for msvcrt.getwch, etc)
    * cursor size and visibility
    * screen-buffer size, font, colors, & attributes
    * window size
    * window title
History
Date User Action Args
2020-10-05 09:47:57eryksunsetrecipients: + eryksun, twoone3
2020-10-05 09:47:56eryksunsetmessageid: <1601891276.99.0.544135252286.issue41941@roundup.psfhosted.org>
2020-10-05 09:47:56eryksunlinkissue41941 messages
2020-10-05 09:47:56eryksuncreate