[issue15347] IDLE - does not close if the debugger was active

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15347] IDLE - does not close if the debugger was active

Terry J. Reedy added the comment: See #15348 for result of fix-mainloop2.patch on Windows. -- ___ Python tracker ___

[issue15347] IDLE - does not close if the debugger was active

Terry J. Reedy added the comment: Git patch does not apply because header does not have full paths. diff --git a/Debugger.py b/Debugger.py index e2014d1..9efe6fa 100644 --- a/Debugger.py +++ b/Debugger.py versus diff -r ed694938c61a Lib/idlelib/Debugger.py --- a/Lib/idlelib/Debugger.py Tue

[issue15347] IDLE - does not close if the debugger was active

Mark Roseman added the comment: Doing some testing using "-n". Various close/quit scenarios are either disallowed or broken as it turns out. I found that removing the "interacting" check on close improved the matter quite substantially, so that I could quit when the debugger was sitting

[issue15347] IDLE - does not close if the debugger was active

Mark Roseman added the comment: See #24455 for a patch that includes the changes from this one as well as some additional changes that fixes that bug. -- ___ Python tracker

[issue15347] IDLE - does not close if the debugger was active

Mark Roseman added the comment: Figured out the cause of this hang, it was to do with the nested event loops. It turns out that mainloop() really should just be for the mainloop. Or at least quit() should only be used to quit the outer loop, as it relies on setting a static variable, so is

[issue15347] IDLE - does not close if the debugger was active

Mark Roseman added the comment: Debugger.py has a nested call to mainloop() ... which is almost always a bad idea. I'm betting the close is being handled in this mainloop, and there are no more events being generated, meaning the real mainloop towards the bottom of PyShell (which checks if

[issue15347] IDLE - does not close if the debugger was active

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

[issue15347] IDLE - does not close if the debugger was active

Terry J. Reedy added the comment: A few years ago there was an issue where starting a new user process left the old user process continuing as a zombie. This time, it seems to be the idle process that becomes the zombie. I determined this by starting Idle in edit-only mode, noting the memory

[issue15347] IDLE - does not close if the debugger was active

Terry J. Reedy added the comment: #21339, closed as a duplicate of this, has a traceback might be helpful. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15347 ___

[issue15347] IDLE - does not close if the debugger was active

Mark Lawrence added the comment: A pythonw.exe process is left running if I try this with 3.4.1 on Windows 7. -- nosy: +BreamoreBoy, terry.reedy versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org

[issue15347] IDLE - does not close if the debugger was active

New submission from Roger Serwy roger.se...@gmail.com: IDLE fails to close if the debugger was active. Steps to reproduce: 1) Start IDLE with only a shell. 2) Enable debugger. 3) Press enter in the shell. (Causes debugger to activate) 4) Close the shell window. (File-Exit or click X) 5) Click