➜

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-09.23:15:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441840538.22.0.99922295675.issue15347@psf.upfronthosting.co.za>
In-reply-to
Content 
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 we've got open windows) is never being reentered. 

Will try to look at this closer, but in case anyone has a chance in the interim...
History
Date User Action Args
2015-09-09 23:15:38markrosemansetrecipients: + markroseman, terry.reedy, roger.serwy, BreamoreBoy, Saimadhav.Heblikar
2015-09-09 23:15:38markrosemansetmessageid: <1441840538.22.0.99922295675.issue15347@psf.upfronthosting.co.za>
2015-09-09 23:15:38markrosemanlinkissue15347 messages
2015-09-09 23:15:38markrosemancreate