traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

#2253: fix continue vs. finally docs.

This commit is contained in:
Georg Brandl 2008-03-08 09:54:06 +00:00
parent 31c6de4f79
commit 47a5aec836
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Doc/reference/simple_stmts.rst
View File

@ -619,9 +619,13 @@ The :keyword:`continue` statement
:keyword:`continue` may only occur syntactically nested in a :keyword:`for` or :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:`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. 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: .. _import:
.. _from: .. _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, :func:`locals` return the current global and local dictionary, respectively,
which may be useful to pass around for use by :keyword:`exec`. 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.