[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: The information missing from this issue is that tcl and tk can be compiled without and with thread support, and that the latter became default in 8.6, which is included with recent 3.x versions. Hence the launch example, as posted on #33257, works for me in

[issue11077] Tkinter is not thread safe

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: This issue was effectively reopened by #33257, with altered versions of TkinterCrash2-2. Serhiy's original thereof fails for me on 2.7.15. I will put details on the new issue. -- ___ Python tracker

[issue11077] Tkinter is not thread safe

Changes by Serhiy Storchaka : -- stage: test needed -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue11077] Tkinter is not thread safe

Changes by Serhiy Storchaka : -- resolution: -> works for me status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mail

[issue11077] Tkinter is not thread safe

Serhiy Storchaka added the comment: I can't reproduce the bug on 2.7.8+, but on 2.7.3 I sometimes got messages like "Exception in thread Thread-26 (most likely raised during interpreter shutdown):" or: File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2204, in create_line File "/usr/lib/py

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: With 3.4.1, (64 bit), I ran, saturated (200 launches?) and closed 4 windows without incident. This extends Alexander's claim, 'not 3.x problem', in msg127648, from 3.2 to 3.4. -- ___ Python tracker

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: Summarizing other messages, it seems that tkinter is intended to be thread-safe (as long tk.mainloop is started in the tk thread) and mostly is until it is not (probably from timing issue). With fresh 2.7.8 install, I ran TkinterCrash2.py. I got the following

[issue11077] Tkinter is not thread safe

Mark Lawrence added the comment: Is this still an issue with 2.7.8 which has presumably had more fixes since 2.7.6? -- nosy: +BreamoreBoy ___ Python tracker ___

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: Is this still a problem with 2.7.6, which has a few hundred bug fixes since 2.7.1. -- ___ Python tracker ___ __

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: tk_v_raw.py is not obviously related to this issue. First, you only use tkinter in the main thread. Second, it works on Windows 7-64, 3.4 Idle. >>> Yes? > abc Got cmd abc Yes? > def Got cmd def Yes? > It also runs in the console on 2.7, 3.3, 3.4. The main prob

[issue11077] Tkinter is not thread safe

Keith Bannister added the comment: Hi, I'm trying to make an application with GNU readline support, and some plots. But it seems that tkInter and raw_input don't play nicely. The attached script (18 lines) crashes immediately on my Mac with SIGABRT and outputs the following: $ python tk_v_ra

[issue11077] Tkinter is not thread safe

Honest Abe added the comment: I have been researching this due to the recurring recommendations, on stackoverflow.com, to use the queue.Queue + after() technique when using multiple threads. ——— >From comments in _tkinter.c: The Tcl interpreter is only valid in the thread that created it, a

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: I am somewhat puzzled by the claim that tkinter *is* thread safe (as opposed to *intended to be*), in the sense of accessing the gui from multiple threads. First, http://www.astro.washington.edu/users/rowen/TkinterSummary.html "all Tkinter access must be from

[issue11077] Tkinter is not thread safe

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11077] Tkinter is not thread safe

Antoine Pitrou added the comment: > As a side note, if Tkinter is intended to be thread safe, the > documentation should say so. Clearly, and in the first paragraph. I'm no Tkinter specialist but, judging by its source code, Tkinter (the Python module) *is* intended to be thread-safe using lo

[issue11077] Tkinter is not thread safe

Antoine Pitrou added the comment: The "UpdateStringProc should not be invoked for type cmdName" message (as quoted above in the traceback) apparently can mean that there's a mismanagement of Tcl reference counts. >From >http://sourceforge.net/tracker/?func=detail&atid=110894&aid=1326087&grou

[issue11077] Tkinter is not thread safe

Scott M added the comment: If it helps, over the many iterations of this test code, there have been two kinds of issues: 1. pythonw.exe crashes with the Windows variant of a SEGV. No traceback, just a crash. These are rare. 2. Evidence of confusion over which string the code should be lookin

[issue11077] Tkinter is not thread safe

Martin v. Löwis added the comment: Tk produces "bad screen distance" in Tk_GetScreenMM (convert string to screen millimeters) and TkGetDoublePixels (convert string to number of pixels) when strtod fails on the string being passed. It also produces the error in SetPixelAny (convert object to p

[issue11077] Tkinter is not thread safe

Antoine Pitrou added the comment: I can't reproduce either, but the latest traceback posted in msg127985 seems to hint at a parameter marshalling problem. "create" is one of the parameters to the called Tk function, but it seemed to be mistaken for another. Since it's arguably threading-relat

[issue11077] Tkinter is not thread safe

Scott M added the comment: The new version runs 40 parabolas, then quits. I usually have to run this version 20 times or so to get the crash, so be patient. In general if it's going to crash it does so in the first 6 or so parabolas. Caveat: creates up to 40 threads, so a bit of a CPU pig. Yo

[issue11077] Tkinter is not thread safe

Martin v. Löwis added the comment: > Is Tkinter's thread safety new? It's supported on Unix since 1.5.1, and on Windows since 2.3. -- ___ Python tracker ___ ___

[issue11077] Tkinter is not thread safe

Scott M added the comment: I'll look into making the crash easier to reproduce this coming week. Is Tkinter's thread safety new? Because after I started getting crashes, I did my due diligence in Google and found a number of people writing about how it was necessary to use a Queue and Tkinter

[issue11077] Tkinter is not thread safe

Martin v. Löwis added the comment: My claim is that Tkinter is thread-safe as it stands. A lot of thought has been put into making Tkinter thread-safe, so if there is any claim to the contrary, we would need more details: what exact Python version is being used, what exact operating system is

[issue11077] Tkinter is not thread safe

Changes by Christoph Gohlke : -- nosy: +cgohlke ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue11077] Tkinter is not thread safe

Terry J. Reedy added the comment: 'Thread' is not found in the somewhat skimpy tkinter doc. Given the general state of Python with threads, I think it reasonable to take 'not thread-safe' as the default, making this a feature request. In any case, the point is moot until there is a tested fix

[issue11077] Tkinter is not thread safe

Alexander Belopolsky added the comment: I converted TkinterCrash2.py to 3.x using 2to3 (result attached as TkinterCrash3.py) and it works with 3.2rc2 just fine. -- Added file: http://bugs.python.org/file20632/TkinterCrash3.py ___ Python tracker

[issue11077] Tkinter is not thread safe

Alexander Belopolsky added the comment: Hmm, either my hand is too slow or my laptop is too fast, but I cannot reproduce the crash. Can you create a non-interactive script? Maybe start a separate thread generating "launch" events? What do you mean by "crash"? Do you get a python backtrace o

[issue11077] Tkinter is not thread safe

Changes by Brian Curtin : -- title: Tkinter is not thread safe (and that's... bad) -> Tkinter is not thread safe ___ Python tracker ___ _

[issue11077] Tkinter is not thread safe (and that's... bad)

Scott M added the comment: I don't have an opinion on 1252236. I'm not certain it would help. I have an extension that runs a bunch of (alien) threads into Python code. The threads deliver information for all sorts of real world events, asynchronously. Multiple threads are used, because peopl

[issue11077] Tkinter is not thread safe

Alexander Belopolsky added the comment: One possible solution was presented in issue1252236: move tkinter event loop into Python main loop. However, to consider this report a bug, we need an example code that shows the behavior that you consider incorrect. Even then, it is likely that fixin

[issue11077] Tkinter is not thread safe

Changes by Brian Curtin : -- title: Tkinter is not thread safe. This is a bug. -> Tkinter is not thread safe ___ Python tracker ___ __

[issue11077] Tkinter is not thread safe. This is a bug.

New submission from Scott M : The more I look at GUI support in Python, the more I realize that the lack of basic thread safety in GUI support is simply a bug. I know Java's Swing has the same thread limitation, but that doesn't make it right. Xlib is thread safe. The Windows SDK is thread saf