[issue14111] IDLE Debugger should handle interrupts
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
[issue10722] IDLE's subprocess didnit make connection ..... Python 2.7
Larry A. Taylor larry.tay...@bankofamerica.com added the comment: I have had this happen to me many times with Windows XP, the standard OS here. Using IDLE and Python 2.7. Some of the time the following applies: I have more than one Python Shell open at the same time. The first Python shell/IDLE with debug is running a long job I don't want to interrupt. A second IDLE edit window is connected to the second Python shell. I set the shell to debug, then to the edit window with the program, and select 'run'. Result: I get the message reported in this issue. Sometimes. It appears to have nothing to do with firewalls. -- nosy: +ltaylor934 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10722 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14105] Breakpoints in debug lost if line is inserted; IDLE
New submission from Larry A. Taylor larry.tay...@bankofamerica.com: My environment is Windows XP, using IDLE and Python 2.7 distribution. Open an IDLE Python shell. Open the file with three lines in it, 1,2 and 3. In IDLE, Set Breakpoint on Line 2. In Shell, set Debug. In IDLE, select run. In the Debug window, click Go. Run stops at line 2, displayed in Debug. Click Quit. Edit the file, inserting a line 0, like: print this is line 0. Save the file Run again, Go in Debug. The breakpoint has disappeared and the debugger does not stop on line 2 (now the third line). It doesn't stop anywhere. Delete line 0, and set breakpoint on line 2 again. At the end of the file, insert a line 4, such as: print this is line 4. Run again, Go in Debug. The breakpoint is preserved, and the debugger stops at line 2. This is inconsistent behavior. I expect that a breakpoint will not disappear, and that it will always point to the same line, moving down when the line moves down. The breakpoint should move up if the line it refers to moves up. -- components: IDLE, Windows files: debug-line-numbers.py messages: 154104 nosy: ltaylor934 priority: normal severity: normal status: open title: Breakpoints in debug lost if line is inserted; IDLE type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file24621/debug-line-numbers.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14105 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
