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 Ivan.Pozdeev, docs@python, markroseman, serhiy.storchaka, terry.reedy
Date 2018-05-15.00:25:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526343937.04.0.682650639539.issue33479@psf.upfronthosting.co.za>
In-reply-to
Content
This seems very complicated. The official line on threads for Tk has always been to make all Tk calls from one thread, which is at least predictable and comprehensible. Is there any reason for Tkinter to suggest anything different?

This ignores the compilation issue of course. FYI, the Tcl core group will probably eliminate the possibility of doing non-threaded builds in the future, though with backwards compatibility issues, that's neither here nor there.
History
Date User Action Args
2018-05-15 00:25:37markrosemansetrecipients: + markroseman, terry.reedy, docs@python, serhiy.storchaka, Ivan.Pozdeev
2018-05-15 00:25:37markrosemansetmessageid: <1526343937.04.0.682650639539.issue33479@psf.upfronthosting.co.za>
2018-05-15 00:25:36markrosemanlinkissue33479 messages
2018-05-15 00:25:35markrosemancreate