➜

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 v+python
Recipients David.Sankel, Matt.Mackall, akira, amaury.forgeotdarc, brian.curtin, christian.heimes, christoph, davidsarah, ezio.melotti, hippietrail, lemburg, mark, mhammond, pitrou, santoso.wijaya, smerlin, ssbarnea, terry.reedy, tim.golden, tzot, v+python, vstinner
Date 2012-05-16.08:57:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337158648.35.0.973763423461.issue1602@psf.upfronthosting.co.za>
In-reply-to
Content 
Has something incompatible changed between 3.2.2 and 3.2.3 with respect to this bug?

I have a program that had an earlier version of the workaround (Michael's original, I think), and it worked fine, then I upgraded from 3.2.2 to 3.2.3 due to testing for issue 14811 and then the old workaround started complaining about no attribute 'errors'.

So I grabbed unicode3.py, but it does the same thing:

AttributeError: 'UnicodeConsole' object has no attribute 'errors'

I have no clue how to fix this, other than going back to Python 3.2.2...
History
Date User Action Args
2012-05-16 08:57:28v+pythonsetrecipients: + v+python, lemburg, mhammond, terry.reedy, tzot, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, mark, christoph, ezio.melotti, hippietrail, ssbarnea, brian.curtin, davidsarah, santoso.wijaya, akira, David.Sankel, smerlin, Matt.Mackall
2012-05-16 08:57:28v+pythonsetmessageid: <1337158648.35.0.973763423461.issue1602@psf.upfronthosting.co.za>
2012-05-16 08:57:27v+pythonlinkissue1602 messages
2012-05-16 08:57:27v+pythoncreate