Author eryksun
Recipients Simon Depiets, eryksun, larry, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-12-09.22:15:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512857736.28.0.213398074469.issue32245@psf.upfronthosting.co.za>
In-reply-to
Content
We need a test that reproduces this problem on a vanilla installation of Python 3.5. Include the system locale context as well, i.e. the ANSI codepage, OEM codepage, and active console output codepage. A reliable test will help determine whether this problem also affects legacy console I/O in Python 3.6. However, even if the problem affects 3.6, that doesn't mean there's anything we can reasonably do about it if the fault is the console host process (i.e. conhost.exe, running either ConhostV1.dll or the new ConhostV2.dll implementation). 

A possible workaround in Python 3.5 would be to install and enable the win_unicode_console package. This package uses the console's native Unicode API instead of the legacy codepage API.
History
Date User Action Args
2017-12-09 22:15:36eryksunsetrecipients: + eryksun, paul.moore, larry, tim.golden, zach.ware, steve.dower, Simon Depiets
2017-12-09 22:15:36eryksunsetmessageid: <1512857736.28.0.213398074469.issue32245@psf.upfronthosting.co.za>
2017-12-09 22:15:36eryksunlinkissue32245 messages
2017-12-09 22:15:36eryksuncreate