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:31:29
SpamBayes Score 0.0021849268
Marked as misclassified No
Message-id <1279323092.32.0.0634079718887.issue9274@psf.upfronthosting.co.za>
In-reply-to
Content
David, that won't work for a reason I'll get into in a bit.

I would drop the priority of this ... Komodo has a had a
Python debugger since late 2000, we only fixed updating
variables while debugging (using the variable viewer) yesterday,
and received fewer than 10 complaints about that over the years.

While looking at the code, something seemed wrong with our
handling of the variables in the interactive shell.  I tested
it, and it failed, and then wrote the standalone Python code
to isolate the problem.

Your solution will work sometimes, but not completely.  When
you're in interactive mode while debugging, you can type arbitrary
Python code, but can also use the variable viewer in the UI to change
variables.  These two functions are handled by different code
paths.

My recommendation is to resolve this as a limitation, and
document the module.
History
Date User Action Args
2010-07-16 23:31:33ericpsetrecipients: + ericp, r.david.murray, docs@python
2010-07-16 23:31:32ericpsetmessageid: <1279323092.32.0.0634079718887.issue9274@psf.upfronthosting.co.za>
2010-07-16 23:31:30ericplinkissue9274 messages
2010-07-16 23:31:30ericpcreate