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 Richard Sheridan
Recipients Richard Sheridan, epaine, gpolo, serhiy.storchaka
Date 2020-07-05.12:30:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593952207.23.0.486991664824.issue41176@roundup.psfhosted.org>
In-reply-to
Content
I'd like to consider one more possibility for future behavior that sort of came to mind while discussing the PR. In current behavior, it is possible to use `willdispatch` to trick `WaitForMainloop` into letting a thread pass through the timeout, where it will eventually wait on a `Tcl_ConditionWait` in `Tkapp_ThreadSend`. 

This could be very efficient default behavior, since no polling is required; the thread just goes when the loop comes up. Is it possible to make this a well-documented feature and default behavior of tkinter? Or would it be too surprising for new and existing users? It would be important to make sure that threads aren't silently getting lost in old programs and new users can figure out they need to call `mainloop`, `doonevent`, or `update` when not on the REPL or the thread will hang.
History
Date User Action Args
2020-07-05 12:30:07Richard Sheridansetrecipients: + Richard Sheridan, gpolo, serhiy.storchaka, epaine
2020-07-05 12:30:07Richard Sheridansetmessageid: <1593952207.23.0.486991664824.issue41176@roundup.psfhosted.org>
2020-07-05 12:30:07Richard Sheridanlinkissue41176 messages
2020-07-05 12:30:07Richard Sheridancreate