8000 PEP 667: Clarify impact on PyEval_GetLocals by ncoghlan · Pull Request #3809 · python/peps · GitHub
[go: up one dir, main page]

Skip to content

PEP 667: Clarify impact on PyEval_GetLocals #3809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Remove stray underscore
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
  • Loading branch information
ncoghlan and JelleZijlstra authored Jun 21, 2024
commit 83d8028cedf9d0b24e7cbdeb16be358332921a38
2 changes: 1 addition & 1 deletion peps/pep-0667.rst
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ cached instance of the new write-through proxy, while the implementation sketch
it would continue to return a dictionary snapshot cached on the frame instance. This
discrepancy was identified while implementing the PEP, and
`resolved by the Steering Council <https://github.com/python/steering-council/issues/245#issuecomment-2179005461>`__
_ in favour of retaining the Python 3.12 behaviour of returning a dictionary snapshot
in favour of retaining the Python 3.12 behaviour of returning a dictionary snapshot
cached on the frame instance.

To avoid confusion when following the reference link from the Python 3.13 What's New
Expand Down
0