Message256605
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. |
|
Date |
User |
Action |
Args |
2015-12-17 13:39:31 | r.david.murray | set | recipients:
+ r.david.murray, loewis, vstinner, ezio.melotti, spaceone |
2015-12-17 13:39:31 | r.david.murray | set | messageid: <1450359571.76.0.197875038077.issue25880@psf.upfronthosting.co.za> |
2015-12-17 13:39:31 | r.david.murray | link | issue25880 messages |
2015-12-17 13:39:31 | r.david.murray | create | |
|