This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author fabioz
Recipients Mark.Shannon, fabioz, ncoghlan, python-dev, vstinner
Date 2021-06-27.12:13:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> > So, it's expected that `some_module` and `v` would be in the locals at this point.

> If a function does not have the local variables `some_module` and `v`, then the change wouldn't be visible to the debugee.
So what difference does it make?

Right now such changes are visible to the debugee in the locals frames if a user does the `exec` and calls `PyFrame_FastToLocals` right afterwards (even if they weren't initially there).

So, it's the difference between being able to import a module and creating/manipulating new variables in an `exec` in any frame (as it works right now) or not being able to make it at all (if that feature is deprecated as is being implied in the PEP).
Date User Action Args
2021-06-27 12:13:55fabiozsetrecipients: + fabioz, ncoghlan, vstinner, Mark.Shannon, python-dev
2021-06-27 12:13:55fabiozsetmessageid: <>
2021-06-27 12:13:55fabiozlinkissue42197 messages
2021-06-27 12:13:55fabiozcreate