Author vstinner
Recipients David.Sankel, Drekin, akira, amaury.forgeotdarc, christian.heimes, christoph, davidsarah, ezio.melotti, flox, giampaolo.rodola, hippietrail, lemburg, mark, mhammond, ncoghlan, pitrou, santoso.wijaya, smerlin, ssbarnea, steve.dower, terry.reedy, tim.golden, tzot, v+python, vstinner
Date 2014-07-25.13:40:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The poor interaction with the Windows command line is still a bug in CPython - we could mark it closed/later but I don't see any value in doing so.

I don't see any value in keeping the issue open since nobody worked on it last 7 years. I just want to make it clear that we will *not* fix this issue.

Well, in fact I spent a lot of hours trying to find a way to fix the issue, and my conclusion is that it's not possible to handle correctly Unicode (input and output) in a Windows console. Please read the whole issue for the detail.

The win_unicode_console project may improve the Unicode support, but I'm convinced that it still has various issues because it is just not possible to handle all cases.

A workaround is to not use the Windows console, but use IDLE or another shell... Try maybe PowerShell. But PowerShell has at least an issue with the code page 65001 (Microsoft UTF-8): see the issue #21927.
Date User Action Args
2014-07-25 13:40:42vstinnersetrecipients: + vstinner, lemburg, mhammond, terry.reedy, tzot, amaury.forgeotdarc, ncoghlan, pitrou, giampaolo.rodola, christian.heimes, tim.golden, mark, christoph, ezio.melotti, v+python, hippietrail, ssbarnea, flox, davidsarah, santoso.wijaya, akira, David.Sankel, smerlin, Drekin, steve.dower
2014-07-25 13:40:42vstinnersetmessageid: <>
2014-07-25 13:40:42vstinnerlinkissue1602 messages
2014-07-25 13:40:42vstinnercreate