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

PEP 558: Fix mention of old locals() semantics (#1266) 

When updating the PEP to specify independent snapshots for locals()
at function scope, I missed this reference to the old semantics
that returned a direct reference to the dynamic internal snapshot.
This commit is contained in:
Nick Coghlan 2020-01-02 02:30:39 +10:00 committed by GitHub
parent 475d6cdf8c
commit 8dcf7fe49c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pep-0558.rst
View File

@ -290,11 +290,11 @@ defined ``locals()`` builtin, trace functions necessarily use the implementation
dependent ``frame.f_locals`` interface, as a frame reference is what gets dependent ``frame.f_locals`` interface, as a frame reference is what gets
passed to hook implementations. passed to hook implementations.
Instead of being a direct reference to the dynamic snapshot returned by Instead of being a direct reference to the internal dynamic snapshot used to
``locals()``, ``frame.f_locals`` will be updated to instead return a dedicated populate the independent snapshots returned by ``locals()``, ``frame.f_locals``
proxy type (implemented as a private subclass of the existing will be updated to instead return a dedicated proxy type (implemented as a
``types.MappingProxyType``) that has two internal attributes not exposed as private subclass of the existing ``types.MappingProxyType``) that has two
part of either the Python or public C API: internal attributes not exposed as part of the Python runtime API:
* *mapping*: an implicitly updated snapshot of the function local variables * *mapping*: an implicitly updated snapshot of the function local variables
and closure references, as well as any arbitrary items that have been set via and closure references, as well as any arbitrary items that have been set via
@ -302,6 +302,9 @@ part of either the Python or public C API:
underlying frame underlying frame
* *frame*: the underlying frame that the snapshot is for * *frame*: the underlying frame that the snapshot is for
For backwards compatibility, the stored snapshot will continue to be made
available through the public ``PyEval_GetLocals()`` C API.
``__getitem__`` operations on the proxy will read directly from the stored ``__getitem__`` operations on the proxy will read directly from the stored
snapshot. snapshot.