Hi Brian,
There are several things to write down about the relationship between
PySide, Spyder and EPD:
1. Spyder 2.0.x doesn't work with PySide. Spyder 2.1 will work with
either PySide or PyQt but it's in beta right now.
2. The minimum required version of PySide is 1.0.7. Previous versions
generate random segfaults (for example, on closing).
3. Spyder doesn't work with EPD 7.1-2, because (as you noticed) it comes
with PySide 1.0.5
And a final remark:
4. Matplotlib 1.0 doesn't work with PySide, though its git master branch
has support for it.
Cheers,
Carlos
El 26/09/11 21:11, Brian Hanna escribió:
Hi all,
I've just gotten spyder to run on our RHEL6 systems! Looks great, but
unfortunately it segfaults on exit.
I have:
epd-7.1-2-rh5-x86_64 (which includes PySide-1.0.5 in site-packages and
Qt-4.7.3 in lib)
spyder-2.0.12
sip-4.12.4
Without understanding PySide and Qt were part of EPD, I had also
downloaded and installed:
Qt-4.7.4 (from Nokia)
PyQt-x11-gpl-4.8.5
With PyQt installed with my EPD, I had a strange segfault with a
backtrace including Qt cores from BOTH PySide and PyQT... it would
crash right after the splash screen.
I moved PyQt aside within EPD site-packages, and now spyder runs with
PySide... but segfaults on exit. I've only done minimal testing so
far.
I'm hearing PySide is not stable yet, and others have seen this
segfault on exit. (Apparently it has been patched in PySide already.)
I'd like to try running spyder with just PyQt.
Any suggestions on how to control what spyder picks for Qt bindings
and libraries?
Thanks,
Brian
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
