From 47a5aec8362e7a78c10528ef565dc0e6fad1c489 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Sat, 8 Mar 2008 09:54:06 +0000 Subject: [PATCH] #2253: fix continue vs. finally docs. --- Doc/reference/simple_stmts.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Doc/reference/simple_stmts.rst b/Doc/reference/simple_stmts.rst index 0767170114..088e9fc5ca 100644 --- a/Doc/reference/simple_stmts.rst +++ b/Doc/reference/simple_stmts.rst @@ -619,9 +619,13 @@ The :keyword:`continue` statement :keyword:`continue` may only occur syntactically nested in a :keyword:`for` or :keyword:`while` loop, but not nested in a function or class definition or -:keyword:`finally` statement within that loop. [#]_ It continues with the next +:keyword:`finally` clause within that loop. It continues with the next cycle of the nearest enclosing loop. +When :keyword:`continue` passes control out of a :keyword:`try` statement with a +:keyword:`finally` clause, that :keyword:`finally` clause is executed before +really starting the next loop cycle. + .. _import: .. _from: @@ -920,9 +924,4 @@ built-in function :func:`eval`. The built-in functions :func:`globals` and :func:`locals` return the current global and local dictionary, respectively, which may be useful to pass around for use by :keyword:`exec`. -.. rubric:: Footnotes - -.. [#] It may occur within an :keyword:`except` or :keyword:`else` clause. The - restriction on occurring in the :keyword:`try` clause is implementor's laziness - and will eventually be lifted. -- 2.40.0