Closed GoogleCodeExporter closed 9 years ago
All pyscripter is doing is evaluating the identifier under the cursor in the
scope of the selected frame in the Call Stack. The Call Stack frames which
contain information about variable values do not necessarily relate to the
scopes of the code and it would be hard to do anything more sophisticated here.
So all PyScripter is doing is eval("x". frame.locals, frame.globals)
However PyScripter can help you, in your example, to see the values of all 3 x
variables using debugger hints. If say you break execution using a breakpoint
inside the function g your call stack will will look like:
g
f
main
module
Debugger hint on x (any x) will show [20, 30, 40]
In the Call Stack Window click on f.
Debugger hint on x will show 3
In the Call Stack Window click on main.
Debugger hint on x will show 42
Original comment by pyscripter
on 31 Aug 2010 at 11:20
Original issue reported on code.google.com by
cspwc...@gmail.com
on 30 Aug 2010 at 5:44