[issue16823] Python quits on running tkinter code with threads

Change by Terry J. Reedy : -- resolution: -> duplicate ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue16823] Python quits on running tkinter code with threads

Terry J. Reedy added the comment: In the message above, I asked "why this code runs in 3.x but eventually fails in 2.x?". The answer is almost certainly that I used 3.5 with tk 8.6 compiled *with* thread support and 2.7 with tk 8.5 compiled without thread support. Serhiy, if you use a system

[issue16823] Python quits on running tkinter code with threads

Serhiy Storchaka added the comment: I don't know. I'm unable to reproduce the bug on Linux. -- ___ Python tracker ___ ___ Python-bugs-

[issue16823] Python quits on running tkinter code with threads

Changes by Terry J. Reedy : -- versions: +Python 3.5 -Python 3.2, Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list m

[issue16823] Python quits on running tkinter code with threads

Terry J. Reedy added the comment: If I understand the test code, it creates the tk window in thread 0 (the main thread), generates data in thread 1, sends data via a queue to thread 2, which then inserts it into the Text widget. I ran a 3.x version up to 34000 iterations. When I comment out

[issue16823] Python quits on running tkinter code with threads

Terry J. Reedy added the comment: >From #11029: Doc about tkinter and treads should also give the alternative of >using queue.queue to feed data from multiple threads. See msg127316 -- ___ Python tracker _

[issue16823] Python quits on running tkinter code with threads

Terry J. Reedy added the comment: We use 'crash' to mean a segfault (and core dump, on *nix) or the Windows equivalent. We avoid those if at all possible. A Python traceback is not a crash but a semi-graceful shutdown that has be planned for, given the circumstances. What is annoying here is g