-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Don't access current_frame f_locals #13021
Conversation
This should fix ipython#13020 Though it's a suttle enough bug that tests needs to be written. And we can't rely on doctests as they are not ran.
I'm still not sure if I understand why accessing I wonder why I never noticed this. |
This is probably related, but Pdb in cpython use self.curframe_locals as well, so it's likely on purpose. |
Test added. |
Co-authored-by: Blazej Michalik <6691643+MrMino@users.noreply.github.com>
For anyone interested, and for the future me - it's the call to This has few other funny quirks that might bite us in the future, if pdb fixes any and we manage to shadow the patch in ipdb. There's a draft PEP for fixing the |
…021-on-7.x Backport PR #13021 on branch 7.x (Don't access current_frame f_locals)
This should fix #13020
Though it's a suttle enough bug that tests needs to be written.
And we can't rely on doctests as they are not ran.