[SciPy-dev] Plan for releasing Scipy 0.3.2
pearu at scipy.org
Wed Oct 6 17:19:26 CDT 2004
On Wed, 6 Oct 2004, Fernando Perez wrote:
> I worry that gui_thread is really not ready for public consumption:
> planck[pylab]> cd /usr/share/doc/wxPythonGTK2-188.8.131.52/demo/
> planck[demo]> ip
> Python 2.3.3 (#1, May 7 2004, 10:31:40)
> Type "copyright", "credits" or "license" for more information.
> IPython 0.6.4.rc1 -- An enhanced Interactive Python.
> ? -> Introduction to IPython's features.
> %magic -> Information about IPython's 'magic' % functions.
> help -> Python's own help system.
> object? -> Details about 'object'. ?object also works, ?? prints more.
> In : import gui_thread
> In : gui_thread.start()
> In : import Main
> In : d = Main.wxPythonDemo(None,-1, 'a')
> Segmentation fault
> Prabhu is getting very good results with wxpython 2.5, but it seems that for
> 2.4 there are serious problems still. I've been running several small tests
> which he has suggested, but with no positive results yet.
> Considering that this is on an up-to-date Fedora 2 install, perhaps
> gui_thread should be disabled for WxPython 2.4. Printing a warning and
> telling users that gui_thread only supports 2.5 would be better than
> segfaulting :)
I have no problems with using gui_thread on a Debian system with
wxPythonSrc-184.108.40.206. So, I wouldn't disable gui_thread for myself;)
My environment: Python 2.3.4, LANG is unset, Numeric 23.5.
Could you try to use libwadpy or some other tool to find out which part of
wxPython is segfaulting?
More information about the Scipy-dev