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.
IDLEfork README
===============
IDLEfork is an official experimental fork of Python's Integrated DeveLopment
Environment, IDLE. The biggest change is to execute Python code in a separate
process, which is /restarted/ for each Run (F5) initiated from an editor
window. This enhancement of IDLE has often been requested, and is now finally
available, complete with the IDLE debugger. The magic "reload/import *"
incantations are no longer required when editing/testing a module two or three
steps down the import chain.
There is also a new GUI configuration manager which makes it easy to select
fonts, colors, keybindings, and startup options. There is new feature where
the user can specify additional help sources, either locally or on the web.
IDLEfork will be merged back into the Python distribution in the near future
(probably 2.3), replacing the current version of IDLE.
For information on this release, refer to NEWS.txt
As David Scherer aptly put it in the original IDLEfork README, "It is alpha
software and might be unstable. If it breaks, you get to keep both pieces."
If you find bugs let us know about them by using the IDLEfork Bug Tracker. See
the IDLEfork home page at
http://idlefork.sourceforge.net
for details. Patches are always appreciated at the IDLEfork Patch Tracker, and
Change Requests should be posted to the RFE Tracker at
https://sourceforge.net/tracker/?group_id=9579&atid=359579
There is a mail list for IDLE: idle-dev@python.org. You can join at
http://mail.python.org/mailman/listinfo/idle-dev
Thanks for trying IDLEfork.
bc2861313c