New submission from Larry A. Taylor <larry.tay...@bankofamerica.com>:
The attached script runs a long processing loop. Start it in IDLE. Open the script and run it. Press control-C. Result: message, KeyboardInterrupt with traceback message. In shell window, turn on Debugger. Run the script. Press control-C. Result: Restrat message shown in Python Shell. Debug Control shows no change. Expected behavior: For keyboard interrupt, or for any uncaught exception, Debug Control should show the same information as if there was a breakpoint. For instance, the stack with line numbers, locals and globals. Better: make a way to interrupt the program in a long loop or process, so that the programmer can tell -- live -- where the program is, and where most of the time is being used. Then use the regular buttons, Go, etc. to continue the process, possibly interrupted again. Also: the IDLE Python Shell and Debug Control show no "running" indicator, so there is no easy way to tell if the program is still going. ---------- components: IDLE, Windows files: debug-running-or-stopped.py messages: 154150 nosy: ltaylor934 priority: normal severity: normal status: open title: IDLE Debugger should handle interrupts type: enhancement versions: Python 2.7 Added file: http://bugs.python.org/file24631/debug-running-or-stopped.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14111> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
