➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author markroseman
Recipients BreamoreBoy, Saimadhav.Heblikar, markroseman, roger.serwy, terry.reedy
Date 2015-09-25.21:06:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443215182.58.0.627007728603.issue15347@psf.upfronthosting.co.za>
In-reply-to
Content 
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 waiting for input, without hangs etc.

Have attached remove-interacting-debugger.patch (which can be applied on top of fix-mainloop2.patch (from #24455, which includes the changes in fix-nested-mainloop.patch for this bug).
History
Date User Action Args
2015-09-25 21:06:22markrosemansetrecipients: + markroseman, terry.reedy, roger.serwy, BreamoreBoy, Saimadhav.Heblikar
2015-09-25 21:06:22markrosemansetmessageid: <1443215182.58.0.627007728603.issue15347@psf.upfronthosting.co.za>
2015-09-25 21:06:22markrosemanlinkissue15347 messages
2015-09-25 21:06:22markrosemancreate