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 ethan.furman
Recipients draghuram, eric.araujo, ethan.furman, mrabarnett, ncoghlan, pitrou, poke, rhettinger, steven.daprano
Date 2010-12-29.17:29:56
SpamBayes Score 1.64297e-08
Marked as misclassified No
Message-id <1293643798.16.0.524910862184.issue6210@psf.upfronthosting.co.za>
In-reply-to
Content
> I said the *except* block, not the *try* block ;)

Ah.  So you did.

Okay, if I'm understanding correctly, the scenario you are talking about involves the code in the except block calling some other function, and that other function is raising an exception...  seems unlikely that this would be a case of transforming one exception into another, therefore the raise should not suppress the context by default...  okay, I'll concede the point.

Looks like the best option, then, is Nick's idea of the .no_context() method on exceptions.
History
Date User Action Args
2010-12-29 17:29:58ethan.furmansetrecipients: + ethan.furman, rhettinger, ncoghlan, pitrou, draghuram, eric.araujo, mrabarnett, steven.daprano, poke
2010-12-29 17:29:58ethan.furmansetmessageid: <1293643798.16.0.524910862184.issue6210@psf.upfronthosting.co.za>
2010-12-29 17:29:56ethan.furmanlinkissue6210 messages
2010-12-29 17:29:56ethan.furmancreate