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 mrabarnett
Recipients draghuram, ethan.furman, mrabarnett, ncoghlan, pitrou, poke, rhettinger, steven.daprano
Date 2010-12-28.03:31:24
SpamBayes Score 0.000536013
Marked as misclassified No
Message-id <1293507088.37.0.677522632654.issue6210@psf.upfronthosting.co.za>
In-reply-to
Content
Regarding syntax, I'm undecided between:

    raise with new_exception

and:

    raise new_exception with caught_exception

I think that the second form is clearer:

    try:
        ...
    exception SomeException as ex:
        raise SomeOtherException() with ex

(I'd prefer 'with' to Steven's 'from') but the first form doesn't force you to provide a name:

    try:
        ...
    exception SomeException:
        raise with SomeOtherException()

and the syntax also means that you can't chain another exception like this:

    try:
        ...
    exception SomeException as ex:
        raise SomeOtherException() with YetAnotherException()

although perhaps Python should just rely on the programmer's good judgement. :-)
History
Date User Action Args
2010-12-28 03:31:28mrabarnettsetrecipients: + mrabarnett, rhettinger, ncoghlan, pitrou, draghuram, steven.daprano, poke, ethan.furman
2010-12-28 03:31:28mrabarnettsetmessageid: <1293507088.37.0.677522632654.issue6210@psf.upfronthosting.co.za>
2010-12-28 03:31:24mrabarnettlinkissue6210 messages
2010-12-28 03:31:24mrabarnettcreate