Author v+python
Recipients David.Sankel, akira, amaury.forgeotdarc, christian.heimes, christoph, davidsarah, ezio.melotti, giampaolo.rodola, hippietrail, lemburg, mark, mhammond, pitrou, santoso.wijaya, smerlin, sorin, terry.reedy, tim.golden, tzot, v+python, vstinner
Date 2012-07-03.19:54:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341345274.83.0.534415385942.issue1602@psf.upfronthosting.co.za>
In-reply-to
Content
Terry said:
Is unicode3.py something to run once or import in each app that wants unicode output? 

I say:
The latter... import it.

Terry said:
Either way, if it is possible to fix the console, why is it not distribute it with the fix?

I say:
Not sure what you are asking here. Yes it is possible to fix the console, but this fix depends on the version-specific internals of the Python IO system... so unicode3.py works with Python 3.1, but not Python 3.2 or 3.3.  I haven't tested to see if my patched unicode3.py still works on Python 3.1 (I imagine it would, due to the nature of the fix just adding something that Python 3.1 probably would ignore.

So my opinion is the fix is better done inside Python than inside the application.
History
Date User Action Args
2012-07-03 19:54:34v+pythonsetrecipients: + v+python, lemburg, mhammond, terry.reedy, tzot, amaury.forgeotdarc, pitrou, vstinner, giampaolo.rodola, christian.heimes, tim.golden, mark, christoph, ezio.melotti, hippietrail, sorin, davidsarah, santoso.wijaya, akira, David.Sankel, smerlin
2012-07-03 19:54:34v+pythonsetmessageid: <1341345274.83.0.534415385942.issue1602@psf.upfronthosting.co.za>
2012-07-03 19:54:34v+pythonlinkissue1602 messages
2012-07-03 19:54:33v+pythoncreate