diff options
author | Kurt B. Kaiser <kbk@shore.net> | 2003-01-25 21:33:40 (GMT) |
---|---|---|
committer | Kurt B. Kaiser <kbk@shore.net> | 2003-01-25 21:33:40 (GMT) |
commit | bc2861313cc53711d837a0e8a5bf303bf5291bf3 (patch) | |
tree | 3d778a44cb78b61adff76b42b70e5dd600aa7ec9 /Lib/test/test_minidom.py | |
parent | cd5c8c2120b1de34cf0d0d04662248c77372bfdd (diff) | |
download | cpython-bc2861313cc53711d837a0e8a5bf303bf5291bf3.zip cpython-bc2861313cc53711d837a0e8a5bf303bf5291bf3.tar.gz cpython-bc2861313cc53711d837a0e8a5bf303bf5291bf3.tar.bz2 |
M PyShell.py
M RemoteDebugger.py
M rpc.py
Fix the incorrect shell exception tracebacks generated when running
under debugger control:
1. Use rpc.SocketIO.asynccall() instead of remotecall() to handle the
IdbProxy.run() command.
2. Add a 'shell' attribute to RemoteDebugger.IdbProxy to allow setting
of ModifiedInterpreter's active_seq attribute from RemoteDebugger code.
3. Cleanup PyShell.ModifiedInterpreter.runcode() and remove ambiguity
regarding use of begin/endexecuting().
4. In runcode() and cleanup_traceback() use 'console' instead of 'file' to
denote the entity to which the exception traceback is printed.
5. Enhance cleanup_traceback() so if the traceback is pruned entirely away
(the error is in IDLE internals) it will be displayed in its entirety
instead.
6. ModifiedInterpreter.runcode() now prints ERROR RPC returns to both
console and __stderr__.
7. Make a small tweak to the rpc.py debug messages.
Diffstat (limited to 'Lib/test/test_minidom.py')
0 files changed, 0 insertions, 0 deletions