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 ericp
Recipients docs@python, ericp, r.david.murray
Date 2010-07-16.23:14:45
SpamBayes Score 0.007703999
Marked as misclassified No
Message-id <1279322088.55.0.113144414925.issue9274@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the response.

Note that our use case *is* to implement Python-console
functionality, but sometimes we do this in the context
of a currently running Python program, inside a function.
That's why I wrote the repro that way.  Using
code.InteractiveInterpreter(locals()).runsource(...)
in a function corresponds to interacting with the
debugger in a function, while the second call to
runsource() corresponds to interacting with the
program when it's stepping through top-level code.

Keep in mind that all of this takes place while
control flow of the main program is stuck in the
debugger's read-eval-print loop.

It would be useful if there was a way of accessing the
localsplus container in Python code
History
Date User Action Args
2010-07-16 23:14:48ericpsetrecipients: + ericp, r.david.murray, docs@python
2010-07-16 23:14:48ericpsetmessageid: <1279322088.55.0.113144414925.issue9274@psf.upfronthosting.co.za>
2010-07-16 23:14:46ericplinkissue9274 messages
2010-07-16 23:14:45ericpcreate