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, ethan.furman, mrabarnett, ncoghlan, pitrou, poke, rhettinger, steven.daprano
Date 2010-12-29.00:06:16
SpamBayes Score 2.63385e-10
Marked as misclassified No
Message-id <1293581178.52.0.123219068672.issue6210@psf.upfronthosting.co.za>
In-reply-to
Content
> And what if the exception is raised from a subroutine?

Well, if I have it surrounded by a try/except block, presumably I'm aware that an exception could be raised.  ;)

And if I'm aware that an exception could be raised, it may also be possible that I want to change the exception -- leading to the three possibilities I described earlier.  

Looking through my dbf module, most of those re-raises I'll be changing to use the raise ... from ... syntax, but there are still a couple places where it makes no sense to have the extra nested information available.
History
Date User Action Args
2010-12-29 00:06:18ethan.furmansetrecipients: + ethan.furman, rhettinger, ncoghlan, pitrou, draghuram, mrabarnett, steven.daprano, poke
2010-12-29 00:06:18ethan.furmansetmessageid: <1293581178.52.0.123219068672.issue6210@psf.upfronthosting.co.za>
2010-12-29 00:06:16ethan.furmanlinkissue6210 messages
2010-12-29 00:06:16ethan.furmancreate