Scott M added the comment:
7 years and counting...
My need for a fix is long gone, but I'd like to be able to tell the original
group I worked with whether it's now safe to use tkinter from threads. It looks
like my original guesses were validated and a fix has been made, but I c
Change by Scott M :
--
nosy: +PythonInTheGrass
___
Python tracker
<https://bugs.python.org/issue33257>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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 CP
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
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 use
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
Scott M added the comment:
Alright. More digging turned up the Tkinter "after" function, aka WM_TIMER for
Windowy people like me, and that plus a nonblocking queue get() gets all my
drawing operations back into the mainLoop() thread. Voilà, no more crashes.
Let me suggest tha
Scott M added the comment:
OK, now all calls to Tkinter are funneled to a single thread, through a queue.
(Technically there are two threads in Tkinter - one is parked in .mainloop(),
the other makes a call to Canvas.create_line and a call to Label.config.)
Different crash, but still a crash
Scott M added the comment:
To make this more interesting, I'm trying to push for adoption of Python at a
scripting tool where I work, and I uncovered this crasher in example code I was
about to hand out, under the heading of "look how easy Python is". For obvious
reasons I&#
New submission from Scott M :
Running on dual core Windows XP.
The function should draw a parabolicish shape for each click on launch. But if
you click Launch over and over, very fast, you get bizarre crashes instead:
Python.exe has encoutered a problem, yadda. tcl85.dll. It rarely takes
Scott M added the comment:
Moving to 3.x means redoing large swaths of the extension I just wrote. It's
only a couple thousand lines, but it was my first extension and it cost me a
week of my life in Google, and it does a lot with strings.
I haven't pulled down the source code fo
Scott M added the comment:
It hasn't failed yet when run "straight".
Here's the issue, though. I'm going to be introducing Python as the scripting
language of choice, to a bunch of people who are less than fluent in
programming. Because debugging is not an obvious
New submission from Scott M :
New to Python; be gentle if I've simply missed something. i'M running on
Windows XP, using a recently downloaded 2.7.1. I'm running by hitting F5 in
IDLE.
The attached .py creates 2 threads, one which updates a Tkinter label 10 times
a second f
14 matches
Mail list logo
