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 Sarbjit.singh, docs@python, gpolo, roger.serwy, terry.reedy
Date 2013-01-05.02:40:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357353620.53.0.734078556438.issue16823@psf.upfronthosting.co.za>
In-reply-to
Content
What you are doing appears to be unsupported (invalid). From
http://www.astro.washington.edu/users/rowen/TkinterSummary.html
"all Tkinter access must be from the main thread (or more precisely,
from the thread that calls the mainloop). Violating this is likely to
cause nasty and mysterious symptoms such as freezes and core dumps."

There have been at multiple posts on python-list and stack overflow from other users that have run into this limitation. I cannot find it in our tkinter docs, but I think perhaps it should be (even though not-thread-safe is the default for any python structure).
History
Date User Action Args
2013-01-05 02:40:20terry.reedysetrecipients: + terry.reedy, gpolo, roger.serwy, docs@python, Sarbjit.singh
2013-01-05 02:40:20terry.reedysetmessageid: <1357353620.53.0.734078556438.issue16823@psf.upfronthosting.co.za>
2013-01-05 02:40:20terry.reedylinkissue16823 messages
2013-01-05 02:40:19terry.reedycreate