➜

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 r.david.murray
Recipients ezio.melotti, loewis, r.david.murray, spaceone, vstinner
Date 2015-12-17.13:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450359571.76.0.197875038077.issue25880@psf.upfronthosting.co.za>
In-reply-to
Content 
Can you explain why it makes error handling hard?  I'm still not seeing the use case.  I've always viewed UnicodeEncodeError vs UnicodeDecodeError as "extra" information for the consumer of the error message, not something that matters in code (I just catch UnicodeError).

I'm not objecting to the change, but it might be nice to know why Martin chose plain UnicodeError, if he's got the time to answer.
History
Date User Action Args
2015-12-17 13:39:31r.david.murraysetrecipients: + r.david.murray, loewis, vstinner, ezio.melotti, spaceone
2015-12-17 13:39:31r.david.murraysetmessageid: <1450359571.76.0.197875038077.issue25880@psf.upfronthosting.co.za>
2015-12-17 13:39:31r.david.murraylinkissue25880 messages
2015-12-17 13:39:31r.david.murraycreate