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 vstinner
Recipients vstinner
Date 2015-03-24.14:46:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427208398.07.0.296272231355.issue23763@psf.upfronthosting.co.za>
In-reply-to
Content
> For the next step, I propose to explicitly clear the current exception before raising a new exception.

Attached pyerr_match_clear.patch implements this. It's only a work-in-progress. I prefer to get feedback on the patch before finishing it.

The patch checks also which exception was raised using PyErr_ExceptionMatches() to avoid hiding import exceptions.

Since my patch makes assumption on which exception is expected, it can change the behaviour of functions if I forgot a different exception which is also supposed to be replaced. Example: only catch ValueError and replace it with ValueError, whereas OverflowError must also be replaced with ValueError.
History
Date User Action Args
2015-03-24 14:46:38vstinnersetrecipients: + vstinner
2015-03-24 14:46:38vstinnersetmessageid: <1427208398.07.0.296272231355.issue23763@psf.upfronthosting.co.za>
2015-03-24 14:46:38vstinnerlinkissue23763 messages
2015-03-24 14:46:37vstinnercreate