➜

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 Ivan.Pozdeev, serhiy.storchaka, terry.reedy
Date 2018-05-03.01:35:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525311356.38.0.682650639539.issue33257@psf.upfronthosting.co.za>
In-reply-to
Content 
I reproduced the error on installed 2.7.14, running tk 8.5.18.

I ran TkinterCrash3-2-2.py 15 times on 64-bit Win10, installed x64 3.6.5, with tk 8.6.8, and experienced no crashes. I ran it another 10 times with 32-bit repository 3.8 debug and no crashes.  My conclusion: this is at least partly a tcl/tk issue fixed in current tcl/tk.

"this would affect any branch if built with nonthreaded Tcl."  If python is delivered (on Windows and Mac) with 'threaded tcl' and rebuilding with 'nonthreaded tcl' causes a problem with tkinter, then one should not do that.  In practice, essentially no one does so.

Serhiy, do you know what type of tcl/tk is distributed on Linux?
History
Date User Action Args
2018-05-03 01:35:56terry.reedysetrecipients: + terry.reedy, serhiy.storchaka, Ivan.Pozdeev
2018-05-03 01:35:56terry.reedysetmessageid: <1525311356.38.0.682650639539.issue33257@psf.upfronthosting.co.za>
2018-05-03 01:35:56terry.reedylinkissue33257 messages
2018-05-03 01:35:54terry.reedycreate