Message237493
For the Python 3 case, the documentation is vague and probably wrong, depending on what you understand “the current scope” to mean. I think it should read something like
. . . raise re-raises the current exception that is being handled. If no exception is being handled, a RuntimeError exception is raised indicating that this is an error.
I’m not sure but I suspect Python 2 is different because does not save the original exception when it handles a nested exception. In other words, at the point where the nested “bar” exception is raised inside the “foo” handler, Python forgets that “foo” was being handled. |
|
Date |
User |
Action |
Args |
2015-03-08 01:49:13 | martin.panter | set | recipients:
+ martin.panter, collinwinter, SilentGhost, a3nm |
2015-03-08 01:49:13 | martin.panter | set | messageid: <1425779353.45.0.72777012309.issue23556@psf.upfronthosting.co.za> |
2015-03-08 01:49:13 | martin.panter | link | issue23556 messages |
2015-03-08 01:49:12 | martin.panter | create | |
|