Author v+python
Recipients BreamoreBoy, David.Sankel, amaury.forgeotdarc, brian.curtin, christian.heimes, christoph, davidsarah, ezio.melotti, lemburg, mark, pitrou, sorin, tim.golden, tzot, v+python, vstinner
Date 2011-01-10.02:27:28
SpamBayes Score 0.000113113
Marked as misclassified No
Message-id <1294626451.69.0.775421210982.issue1602@psf.upfronthosting.co.za>
In-reply-to
Content
I would certainly be delighted if someone would reopen this issue, and figure out how to translate unicode2.py to Python internals so that Python's console I/O on Windows would support Unicode "out of the box".

Otherwise, I'll have to include the equivalent of unicode2.py in all my Python programs, because right now, I'm including instructions for the use to (1) choose Lucida or Consolas font if they can't figure out any other font that gets rid of the square boxes (2) chcp 65001 (3) set PYTHONIOENCODING=UTF-8

Having this capability inside Python (or my programs) will enable me to eliminate two-thirds of the geeky instructions for my users.  But it seems like a very appropriate capability to have within Python, especially Python 3.x with its preference and support Unicode in so many other ways.
History
Date User Action Args
2011-01-10 02:27:31v+pythonsetrecipients: + v+python, lemburg, tzot, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, mark, christoph, ezio.melotti, sorin, brian.curtin, davidsarah, BreamoreBoy, David.Sankel
2011-01-10 02:27:31v+pythonsetmessageid: <1294626451.69.0.775421210982.issue1602@psf.upfronthosting.co.za>
2011-01-10 02:27:28v+pythonlinkissue1602 messages
2011-01-10 02:27:28v+pythoncreate