Author terry.reedy
Recipients Ivan.Pozdeev, serhiy.storchaka, terry.reedy
Date 2018-05-06.05:56:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525586213.42.0.682650639539.issue33412@psf.upfronthosting.co.za>
In-reply-to
Content
When I closed the main thread by clicking [x], thus destroying root, both event threads raised instead of hanging.  So my experiment involved calling root.destroy instead of setting running to False.  The better result when running under IDLE might be due to IDLE's run process executes tcl.call('update') about 20 times per second.  Even if the exception idea could be made to work, it seems like a kludge.

Waiting on the event threads from a separate non-gui thread and leaving the main thread fully functional and responsive until the gui threads die seems much cleaner.  Perhaps this should be recommended as a standard way to shut down the main thread when there might be active gui threads.  Thank you for following through with this to get a solution we both like.
History
Date User Action Args
2018-05-06 05:56:53terry.reedysetrecipients: + terry.reedy, serhiy.storchaka, Ivan.Pozdeev
2018-05-06 05:56:53terry.reedysetmessageid: <1525586213.42.0.682650639539.issue33412@psf.upfronthosting.co.za>
2018-05-06 05:56:53terry.reedylinkissue33412 messages
2018-05-06 05:56:52terry.reedycreate