New submission from Terry J. Reedy: To be more specific: if one runs a file, the shell is restarted (with the file name). In the file, raise SystemExit is normally the same as running off the end of the file, and a prompt is printed. If one runs a file with debugger on, [DEBUG ON] is printed before the prompt. However, SystemExit while debugging causes a Restart Shell before the [DEBUG ON] and >>> prompt. The 2nd restart does not normally happen when debugging finishes. It does not happen when any other exception is raised; instead a traceback is printed as normal.
This is a minor bug, but it does prevent interactive examination of the process after debugging. There is special code in run.py to catch SystemExit and not print a traceback. My guess in a bug in RemoteDebugger.py that causes (allows) the execution process to exit or otherwise get detached from the IDLE process. When the IDLE process loses contact with the current execution process, it starts a new one. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26949> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
