[PyQt] segfaults in a couple libraries with sip 4.7.6 and pyqt4 4.4.2 on linux

2008-05-23 Thread Erick Tryzelaar
We're running fedora core 5, and we're getting some segfaults when we try to import the following libraries: PyQt.Qt, PyQt4.QtHelp, PyQt4.QtOpenGL, PyQt4.QtSql, and PyQt4.QtSvg. The others work fine. This is happening with python 2.4, qt 4.4.0, sip 4.7.6, and pyqt4 4.4.2. Here's a stack trace for

[PyQt] Re: PyQt 4.4.2 GPL installer / missing DLL

2008-05-23 Thread Phil Thompson
On Friday 23 May 2008 6:47:11 pm Pierre Raybaut wrote: > About this missing DLL issue, the main difference between the 4.3.3 and > 4.4.x Windows installer releases seems to be about the .dll management. > Apparently, since 4.4.1 release, for example, there is not only a > QtCore.pyd file but also a

[PyQt] Re: PyQt 4.4.2 GPL installer / missing DLL

2008-05-23 Thread Pierre Raybaut
About this missing DLL issue, the main difference between the 4.3.3 and 4.4.x Windows installer releases seems to be about the .dll management. Apparently, since 4.4.1 release, for example, there is not only a QtCore.pyd file but also a QtCore4.dll and so on. Hence the new "add to path" installer f

Re: [PyQt] PyQt backward compatiblity

2008-05-23 Thread Phil Thompson
On Friday 23 May 2008 5:41:20 pm Jul wrote: > Hello, > > I'm trying to install the last PyQt release (4.4.2) from sources over an > older Qt version (4.2.1). My Qt version is provided by standard CentOS > distribution, and I would prefer not reinstalling it from sources. When I > compile PyQt, it f

Re: [PyQt] QThread problem using PyQt4.4.2

2008-05-23 Thread Stanislas Marquis
2008/5/23 Matt Newell <[EMAIL PROTECTED]>: ... > Does it consistently error on the first import or variable use, or is it > somewhat random? > > Matt > Difficult to say wether it's random, but I think yes, this is the first import (according to urllib.py) after the run() method. And it's the first

[PyQt] PyQt backward compatiblity

2008-05-23 Thread Jul
Hello, I'm trying to install the last PyQt release (4.4.2) from sources over an older Qt version (4.2.1). My Qt version is provided by standard CentOS distribution, and I would prefer not reinstalling it from sources. When I compile PyQt, it fails miserably saying 'qgraphicswidget.h' does not exis

Re: [PyQt] QThread problem using PyQt4.4.2

2008-05-23 Thread Matt Newell
On Friday 23 May 2008 09:06:12 Stanislas Marquis wrote: > Hello all, > I'm facing a problem with threads. The strange part of it is that it > was working fine with PyQt4.3.x. > It seems like inside the thread it's not able to "import" modules or > access variables anymore. All I get is tracebacks l

Re: [PyQt] QThread problem using PyQt4.4.2

2008-05-23 Thread Phil Thompson
On Friday 23 May 2008 5:06:12 pm Stanislas Marquis wrote: > Hello all, > I'm facing a problem with threads. The strange part of it is that it > was working fine with PyQt4.3.x. > It seems like inside the thread it's not able to "import" modules or > access variables anymore. All I get is tracebacks

[PyQt] QThread problem using PyQt4.4.2

2008-05-23 Thread Stanislas Marquis
Hello all, I'm facing a problem with threads. The strange part of it is that it was working fine with PyQt4.3.x. It seems like inside the thread it's not able to "import" modules or access variables anymore. All I get is tracebacks like: Traceback (most recent call last): File "/usr/lib/python2.

Re: [PyQt] PyQt 4.4.2 GPL installer / Silent install not really silent...

2008-05-23 Thread Pierre Raybaut
2008/5/21 Phil Thompson <[EMAIL PROTECTED]>: > On Wednesday 21 May 2008 12:35:39 Python(x,y) wrote: > > 2008/5/21 Phil Thompson <[EMAIL PROTECTED]>: > > > > So my question is: would it be possible to update PATH for all users > > > > without showing this dialog box when the installer is running i

[PyQt] Re: PyQt 4.4.2 GPL installer / missing DLL

2008-05-23 Thread Pierre Raybaut
I know where it comes from: Qt-Eclipse Integration package was interfering with the new PyQt installer... 2008/5/22 Pierre Raybaut <[EMAIL PROTECTED]>: > I didn't have much time to test this, so I must have missed something > (sorry!): in fact, on a fresh Windows XP SP2 install, all is working we