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.
This commit is contained in:
Kurt B. Kaiser 2003-01-25 21:33:40 +00:00
parent cd5c8c2120
commit bc2861313c
3 changed files with 45 additions and 40 deletions

View file

@ -361,9 +361,10 @@ class SocketIO:
seq, resq = message
self.debug("pollresponse:%d:myseq:%s" % (seq, myseq))
if resq[0] == "call":
self.debug("pollresponse:%d:call_localcall" % seq)
self.debug("pollresponse:%d:localcall:call:" % seq)
response = self.localcall(resq)
self.debug("pollresponse:%d:response:%s" % (seq, response))
self.debug("pollresponse:%d:localcall:response:%s"
% (seq, response))
self.putmessage((seq, response))
continue
elif seq == myseq: