New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault on mac os x #711
Comments
Impressive. I wonder if this is a PySide issue. In any case, IPython is written in pure Python code, so we can't directly cause a segfault. |
I bet this is pyside again. We've seen multiple osx crashes, and they are all reported by EPD users (epd ships pyside). @cjw296, is this from an EPD install or did you build the actual PyQT yourself? |
AFAIK, |
yup! OK, I'm closing this bug here simply because it's a pyside crash and there's nothing we can do in IPython about it. But I'm also pinging @epatters at least to make Enthought aware of the issue, I know Evan has done a great job of feeding info back up to Pyside to get things fixed up, and he may find this useful. thanks for your detailed report, I hope it will help the EPD/Pyside folks find a solution. |
Thanks for the report,@fperez, and sorry for the inconvenience. We have recently gotten a few support requests about this, so hopefully it will be resolved soon. |
No worries, @epatters; I know it's not your fault. I just want to give you a heads-up when we get these, so you guys have more info on the state of PySide. Best of luck getting these rough edges smoothed out. |
Following up on this one to keep things linked up - There is a bug in PySide < 1.0.7, where calling |
Glad to hear it, do you know if this is in an EPD release yet? Chris On 01/11/2011 20:08, Min RK wrote:
Simplistix - Content Management, Batch Processing & Python Consulting |
The latest EPD appears to ship with PySide 1.0.5, so no. Keep an eye out |
Hi All,
Here's the crash details
Anything more I can do to help, please let me know...
The text was updated successfully, but these errors were encountered: