Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
gh-118934: Fix PyEval_GetLocals docs (PEP 667)#119932
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
gh-118934: Fix PyEval_GetLocals docs (PEP 667)#119932
Uh oh!
There was an error while loading.Please reload this page.
Conversation
PEP 667's description of the planned changes to PyEval_GetLocalswas internally inconsistent when accepted, so the docs added forpythongh-74929 didn't match either the current behaviour or the intendedbehaviour oncepythongh-118934 is fixed.This PR updates the documentation and 3.13 What's New to match theintended behaviour (oncepythongh-118934 is fixed).
ncoghlan commentedJun 2, 2024
Set to auto-merge, since I don't want to risk the currently incorrect docs making their way into beta2 this week. |
Thanks@ncoghlan for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry,@ncoghlan, I could not cleanly backport this to |
Thanks@ncoghlan for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
PEP 667's description of the planned changes to PyEval_GetLocalswas internally inconsistent when accepted, so the docs added forpythongh-74929 didn't match either the current behaviour or the intendedbehaviour oncepythongh-118934 is fixed.This PR updates the documentation and 3.13 What's New to match theintended behaviour (oncepythongh-118934 is fixed).It also tidies up lingering references to `f_locals` always being adictionary (this hasn't been true since at least when customnamespace support for class statement execution was added)(cherry picked from commitfd6cd62)Co-authored-by: Alyssa Coghlan <ncoghlan@gmail.com>
GH-119934 is a backport of this pull request to the3.13 branch. |
ncoghlan commentedJun 2, 2024
Conflict was due to my failure to merge#119894 yesterday. Fixed that, and retriggered miss-islington |
PEP 667's description of the planned changes to PyEval_GetLocalswas internally inconsistent when accepted, so the docs added forpythongh-74929 didn't match either the current behaviour or the intendedbehaviour oncepythongh-118934 is fixed.This PR updates the documentation and 3.13 What's New to match theintended behaviour (oncepythongh-118934 is fixed).It also tidies up lingering references to `f_locals` always being adictionary (this hasn't been true since at least when customnamespace support for class statement execution was added)
PEP 667's description of the planned changes to PyEval_GetLocalswas internally inconsistent when accepted, so the docs added forpythongh-74929 didn't match either the current behaviour or the intendedbehaviour oncepythongh-118934 is fixed.This PR updates the documentation and 3.13 What's New to match theintended behaviour (oncepythongh-118934 is fixed).It also tidies up lingering references to `f_locals` always being adictionary (this hasn't been true since at least when customnamespace support for class statement execution was added)
PEP 667's description of the planned changes to PyEval_GetLocalswas internally inconsistent when accepted, so the docs added forpythongh-74929 didn't match either the current behaviour or the intendedbehaviour oncepythongh-118934 is fixed.This PR updates the documentation and 3.13 What's New to match theintended behaviour (oncepythongh-118934 is fixed).It also tidies up lingering references to `f_locals` always being adictionary (this hasn't been true since at least when customnamespace support for class statement execution was added)
Uh oh!
There was an error while loading.Please reload this page.
PEP 667's description of the planned changes to PyEval_GetLocals was internally inconsistent when accepted, so the docs added forgh-74929 didn't match either the current behaviour or the intended behaviour oncegh-118934 is fixed.
This PR updates the documentation and 3.13 What's New to match the intended behaviour (oncegh-118934 is fixed).
📚 Documentation preview 📚:https://cpython-previews--119932.org.readthedocs.build/