iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify bullets for Function scope (#403) 

* Clarify bullets for Function scope

* fix backticks
This commit is contained in:
Guido van Rossum 2017-09-08 15:42:12 -07:00 committed by Nick Coghlan
parent f026481062
commit c04dd529ad
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0558.rst
View File

@ -102,8 +102,8 @@ Instead, ``locals()`` is expected to return a mutable *snapshot* of the
function's local variables and any referenced nonlocal cells with the following function's local variables and any referenced nonlocal cells with the following
semantics: semantics:
* each call to ``locals()`` returns the *same* mapping * each call to ``locals()`` returns the *same* mapping object
* each call to ``locals()`` updates the mapping with the current * each call to ``locals()`` updates the mapping to the current
state of the local variables and any referenced nonlocal cells state of the local variables and any referenced nonlocal cells
* changes to the returned mapping are *never* written back to the * changes to the returned mapping are *never* written back to the
local variable bindings or the nonlocal cell references local variable bindings or the nonlocal cell references
@ -115,7 +115,7 @@ For interpreters that provide access to frame objects, the ``frame.f_locals``
attribute at function scope is expected to be a write-through proxy that attribute at function scope is expected to be a write-through proxy that
immediately updates the local variables and reference nonlocal cell bindings. immediately updates the local variables and reference nonlocal cell bindings.
Additional entries may also be added to ``frame.f_locals`` and will be Additional entries may also be added to ``frame.f_locals`` and will be
accessible through both ````frame.f_locals`` and ``locals()`` from inside the accessible through both ``frame.f_locals`` and ``locals()`` from inside the
frame, but will not be accessible by name from within the function (as any frame, but will not be accessible by name from within the function (as any
names which don't appear as local or nonlocal variables at compile time will names which don't appear as local or nonlocal variables at compile time will
only be looked up in the module globals and process builtins, not in the only be looked up in the module globals and process builtins, not in the