PEP 558: remove lingering mentions of the 'view' API (#2204)
This commit is contained in:
parent
dedc9d250e
commit
cb8b62e1d0
|
@ -588,7 +588,7 @@ will be updated only in the following circumstance:
|
|||
operations (``len(flp)``, mapping comparison, ``flp.copy()`` and rendering as
|
||||
a string), as well as those that refresh the cache entries for individual keys.
|
||||
|
||||
Accessing the frame "view" APIs will *not* implicitly update the shared dynamic
|
||||
Requesting a fast locals proxy will *not* implicitly update the shared dynamic
|
||||
snapshot, and the CPython trace hook handling will no longer implicitly update
|
||||
it either.
|
||||
|
||||
|
@ -650,7 +650,7 @@ this PEP incorporates Victor Stinner's proposal to no longer implicitly call
|
|||
``PyFrame_FastToLocalsWithError()`` before calling trace hooks implemented in
|
||||
Python.
|
||||
|
||||
Code using the new frame view APIs will have the dynamic locals snapshot
|
||||
Code using the new fast locals proxy objects will have the dynamic locals snapshot
|
||||
implicitly refreshed when accessing methods that need it, while code using the
|
||||
``PyEval_GetLocals()`` API will implicitly refresh it when making that call.
|
||||
|
||||
|
@ -1032,7 +1032,7 @@ specifically related to the C API:
|
|||
* this PEP adds ``PyLocals_Kind``, ``PyLocals_GetKind()``, and
|
||||
``PyFrame_GetLocalsKind()`` to allow extension modules to identify when code
|
||||
is running at function scope without having to inspect non-portable frame and
|
||||
code objects APIs (without the proposed query API, the existing equivalent to
|
||||
code object APIs (without the proposed query API, the existing equivalent to
|
||||
the new ``PyLocals_GetKind() == PyLocals_SHALLOW_COPY`` check is to include
|
||||
the CPython internal frame API headers and check if
|
||||
``_PyFrame_GetCode(PyEval_GetFrame())->co_flags & CO_OPTIMIZED`` is set)
|
||||
|
|
Loading…
Reference in New Issue