[SciPy-dev] gui_thread issue

Pearu Peterson pearu at scipy.org
Mon Nov 8 03:02:49 CST 2004



On Sun, 7 Nov 2004, Prabhu Ramachandran wrote:

>>>>>> "PP" == Pearu Peterson <pearu at scipy.org> writes:
>
> I suspect that there is one hack that I applied that only fixes a
> 2.5.x related problem that is driving 2.4.x users up the wall.  Could
> you please try this out and see if things improve?

Yes, but got no improvements. I executed the following python session

>>> import gui_thread; gui_thread.start(); import Main
>>> d=Main.wxPythonDemo(None,-1,'a')
>>> ^D

repeately and got different results. Here is the legend for the results 
below:

0 - Demo window appears and is functional, i.e. gui_thread is working OK
1 - Demo window appears but both the window and Python hang
2 - Segmentation fault
3 - Illegal instructions
4 - No demo window, python hangs
5 - Trace/breakpoint trap

> In gui_thread/wxBackgroundApp.py
>
>     94         ExecThread(cmd,globals(),locals())
>     95         finished.wait(0.5)

002021000010022020010320012120220212022424204202502..

> Change line 95 to this:
>
>     95         finished.wait()

42442442224...

So, finished.wait(0.5) is "working" better than finished.wait().
I have tried different hacks on gui_thread but no success yet
to make it stable.

Pearu




More information about the Scipy-dev mailing list