[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: The input glitch mentioned above no longer exists, so closing. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: "not responsive to new commands" means that a statements can be typed but is ignored and no execution takes place. -- ___ Python tracker

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: The patch for #24455 replaced root.mainloop,.quit with tcl vwait, set as the suspend/resume mechanism for Debugger.interation. After this, closing the shell as described in #15347, or the debugger with [x] as described here, on my Windows 10 machine,

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: (I was wrong about seeing the exception when closing the shell.) A major difference between [Quit] and [x] is that [Quit] stops the running program whereas [x] closes the visible gui but leaves the program to run through to the end, as though the [go] button

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roundup Robot added the comment: New changeset 427ad0ede016 by Terry Jan Reedy in branch '2.7': Issue 15348: Stop debugger engine (normally in user process) https://hg.python.org/cpython/rev/427ad0ede016 New changeset 4eae64a9cd26 by Terry Jan Reedy in branch '3.4': Issue 15348: Stop debugger

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: I don't like the idea of [x] flashing quit instead of closing. This patch, on top of the one for #24455, may not be perfect, but the two are definite improvements. Unless I see something critically bad first, I want them in the upcoming releases. Mark

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by Mark Roseman : -- nosy: +markroseman ___ Python tracker ___ ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by irdb electro@gmail.com: -- nosy: +irdb ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___ Python-bugs-list mailing list

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: #24455 is probably related. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___ Python-bugs-list

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by Roger Serwy roger.se...@gmail.com: -- assignee: - roger.serwy versions: +Python 3.4 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: Attached is a patch against 3.4 to solve the issue. The debugger was originally written for running IDLE without a subprocess. As a result, calls to idb.run() from Debugger.py would block until completed. If .interacting == 1 then clicking X would not close the

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: While trying to address #15347, I discovered one too many corner cases where the debugger breaks IDLE. The stable_idle_debugger.diff against 3.4 contains necessary changes to make IDLE more reliable while debugging. Since the IDLE debugger is not documented

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

jimbo1qaz added the comment: Is it possible to make the X button quit the debugger if enabled? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: Clicking X while the debugger is enabled, but not actively debugging a program, will close the debugger window. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

jimbo1qaz added the comment: What's the intended behavior? stop debugging and quit the program? stop debugging and continue freerunning? I'm using 3.3, can you make the patch stop debugging the active running program when you click the X? -- ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: If the debugger is active, then clicking X will flash the Quit button. You must click the quit button first before closing the debugger window. -- ___ Python tracker rep...@bugs.python.org

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

jimbo1qaz added the comment: Then frigging change it! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___ Python-bugs-list mailing list

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: Closing the active debugger with X creates a problem with references and callbacks. I encountered too many corner cases where I could not implement that behavior simply. -- ___ Python tracker rep...@bugs.python.org

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Roger Serwy added the comment: But of course, you are more than welcomed to try to submit a patch yourself. Just make sure that those corner cases I described earlier are handled reasonable when running IDLE with and without a subprocess. -- ___

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Terry J. Reedy added the comment: I have never used the debugger, but I verified the bug. While something was 'hung', the debugger would not restart because something was 'busy'. I also verified that clicking [quit] first and then [x] works. I will try to test the second patch sometime.

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by jimbo1qaz jimmyli1...@gmail.com: -- nosy: +jimbo1qaz ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___ Python-bugs-list

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

New submission from Roger Serwy roger.se...@gmail.com: The IDLE shell does not respond to commands if the debugger window is closed by clicking X. This is due to PyShell's executing flag not being reset. Steps to reproduce: 1) Start IDLE with a shell. 2) Enable debugger. 3) Press enter in the

[issue15348] IDLE - shell becomes unresponsive if debugger windows is closed while active.

Changes by Roger Serwy roger.se...@gmail.com: -- type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15348 ___ ___ Python-bugs-list