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 draghuram, eric.araujo, ethan.furman, mrabarnett, ncoghlan, pitrou, poke, rhettinger, steven.daprano
Date 2010-12-29.08:53:23
SpamBayes Score 9.55861e-08
Marked as misclassified No
Message-id <1293612805.32.0.935262203286.issue6210@psf.upfronthosting.co.za>
In-reply-to
Content
For "can't tell" in my previous message, read "we aren't going to impose the requirement to be able to tell if an exception is being raised directly in the current exception handler as a feature of conforming Python implementations". We probably *could* tell the difference in CPython if we really wanted to.

Even without considering that aspect, it would also be seriously odd if putting the exception raising into a helper function suddenly caused context information to be included that was otherwise implicitly suppressed. Much better to correctly support explicit suppression of the context as discussed earlier in the issue.
History
Date User Action Args
2010-12-29 08:53:25ncoghlansetrecipients: + ncoghlan, rhettinger, pitrou, draghuram, eric.araujo, mrabarnett, steven.daprano, poke, ethan.furman
2010-12-29 08:53:25ncoghlansetmessageid: <1293612805.32.0.935262203286.issue6210@psf.upfronthosting.co.za>
2010-12-29 08:53:24ncoghlanlinkissue6210 messages
2010-12-29 08:53:23ncoghlancreate