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 terry.reedy
Recipients PythonInTheGrass, kbk, pitrou, serhiy.storchaka, terry.reedy
Date 2019-03-08.21:37:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552081029.52.0.486103795801.issue10909@roundup.psfhosted.org>
In-reply-to
Content
I have since learned the following about accessing tk widgets from non-main threads.
1. It seem to be reliable when tcl/tk is compiled with thread support but not when tcl/tk is not so compiled. (The latter is contrary to a claim in the doc.)
2. The tcl default is 'without' 8.5 and 'with' for 8.6, and PSF installers follow the default.  I am guessing that this is likely true for Linux distributions.
3. The 2.7 Windows installer currently includes 8.5.15.  The 3.5+ Windows installers include 8.6.z.  Hence the different results on my Windows machine.
4. Mac installers now use 8.6.z even, I believe, for 2.7.  I have the impression that the system tcl/tk for current Linux distributes is also 8.6.z.
Hence, the issue of tkinter thread safety is resolving itself.

I reran e10909.py with 2.7.16 with the B config call disabled and it ran until I stopped it at 24 minutes.  Printing from a thread is not an issue on my machine.
History
Date User Action Args
2019-03-08 21:37:09terry.reedysetrecipients: + terry.reedy, kbk, pitrou, PythonInTheGrass, serhiy.storchaka
2019-03-08 21:37:09terry.reedysetmessageid: <1552081029.52.0.486103795801.issue10909@roundup.psfhosted.org>
2019-03-08 21:37:09terry.reedylinkissue10909 messages
2019-03-08 21:37:09terry.reedycreate