Message132072
| Author |
gwideman |
| Recipients |
docs@python, gwideman |
| Date |
2011年03月25日.08:42:53 |
| SpamBayes Score |
0.0017726547 |
| Marked as misclassified |
No |
| Message-id |
<1301042574.67.0.975748752077.issue11669@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
In Language Ref section 7 "Compound Statements":
http://docs.python.org/release/3.1.3/reference/compound_stmts.html
there's a footnote regarding what happens to unhandled exceptions in a try-except statement:
[1] The exception is propagated to the invocation stack only if there is no *finally* clause that negates the exception.
This is very unclearly worded, especially since the reader in need of this footnote is probably familiar with the *except* clause being the one to "negate" an exception, and may well think this footnote is in error. This footnote could provide a more convincing explanation:
[1] The exception is propagated to the invocation stack unless there is a finally clause which happens to raise another exception. That new exception causes the old exception to be lost. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年03月25日 08:42:54 | gwideman | set | recipients:
+ gwideman, docs@python |
| 2011年03月25日 08:42:54 | gwideman | set | messageid: <1301042574.67.0.975748752077.issue11669@psf.upfronthosting.co.za> |
| 2011年03月25日 08:42:53 | gwideman | link | issue11669 messages |
| 2011年03月25日 08:42:53 | gwideman | create |
|