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 ncoghlan
Recipients carljm, ncoghlan, serhiy.storchaka
Date 2018-05-19.23:40:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526773257.81.0.682650639539.issue33576@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, the "transparent exception chaining" code falls into the category of code that I'm both proud of (since it works really well in typical cases [1]) and somewhat horrified by (since the *way* it works tramples over several principles of good object oriented design and is completely non-portable to other Python implementations).

Anyway, I've adjusted the issue title here to indicate that we don't want to remove the exception wrapping entirely, just make it less intrusive.

[1] See the hex encoding and bz2 decoding failure examples in https://docs.python.org/3/whatsnew/3.4.html#codec-handling-improvements
History
Date User Action Args
2018-05-19 23:40:57ncoghlansetrecipients: + ncoghlan, carljm, serhiy.storchaka
2018-05-19 23:40:57ncoghlansetmessageid: <1526773257.81.0.682650639539.issue33576@psf.upfronthosting.co.za>
2018-05-19 23:40:57ncoghlanlinkissue33576 messages
2018-05-19 23:40:57ncoghlancreate