[PyQt] Re: autodetect Python.h in configure.py for SIP

2007-06-19 Thread techtonik
The problem is that configure.py uses backward slashes in Makefile for MSYS on Windows platform. [EMAIL PROTECTED] /c/WorkSpace/Eric IDE/Prerequisites/sip-4.6 $ c:/tools/python24/python ./configure.py -p win32-g++ This is SIP 4.6 for Python 2.4.3 on win32. The SIP code generator will be installed

[PyQt] Re: autodetect Python.h in configure.py for SIP

2007-06-19 Thread techtonik
The same thing happens with generated Makefiles. They contain DOS/NT commands even if generated from MSYS environment. Why isn't it possible to use distutils/setuptools or scons instead of reinventing the process? ___ PyQt mailing list

[PyQt] New PyQt book: 1/2 available...

2007-06-19 Thread Mark Summerfield
Hi, Just to let you know that the first half of my new book, Rapid GUI Programming with Python and Qt which is based on Python 2.5, PyQt 4.2 and Qt 4.2, is available online at http://safari.informit.com/9780132354189 The cover can be seen on Amazon:

[PyQt] PyQt4.2 not buildable on win32 using mingw

2007-06-19 Thread Andreas Pakulat
Hi, PyQt4.2's configure.py fails because QMAKE_CFLAGS_THREAD is not set, this variable seems to be not mandatory for win32-g++, although I have to admit that I'm using qt-copy from KDE's svn and not the release tarball. Phil (or anybody else), can you check wether mkspecs/win32-g++/qmake.conf

Re: [PyQt] New PyQt book: 1/2 available...

2007-06-19 Thread Hans-Peter Jansen
Am Dienstag, 19. Juni 2007 17:52 schrieb Mark Summerfield: Hi, Just to let you know that the first half of my new book, Rapid GUI Programming with Python and Qt which is based on Python 2.5, PyQt 4.2 and Qt 4.2, is available online at http://safari.informit.com/9780132354189 Nice. Btw,

[PyQt] PyQT and twisted

2007-06-19 Thread Anita Diliberto
I'm trying to use twisted and QT, but when I close down my application, python continues to run. This is the code I'm using below. Any suggestions? -- from twisted.internet import reactor app =

Re: [PyQt] PyQt4.2 not buildable on win32 using mingw

2007-06-19 Thread Andreas Pakulat
On 19.06.07 21:05:37, Andreas Pakulat wrote: Hi, PyQt4.2's configure.py fails because QMAKE_CFLAGS_THREAD is not set, this variable seems to be not mandatory for win32-g++, although I have to admit that I'm using qt-copy from KDE's svn and not the release tarball. Phil (or anybody else),

[PyQt] PyQt4.2 path issues on win32

2007-06-19 Thread Andreas Pakulat
Hi, so far PyQt4.2 compilation went fine, there's only 1 issue I found: The Qt path for installing the PyQt.api file is not fixed, i.e. it contains unix path-separators (/) instead of win32 ones (\). But only for the directory that configure.py gets from qmake, the separation of

[PyQt] QScintilla's dll is only install qt/lib on win32

2007-06-19 Thread Andreas Pakulat
Hi, I just wanted to install eric4 and the first try to execute python install.py failed because QScintilla's qscintilla2.dll isn't installed into Qt's bin dir. It only is installed into qt/lib and thus applications needing the dll don't start (on windows dll's have to be in PATH) including the

Re: [PyQt] QScintilla's dll is only install qt/lib on win32

2007-06-19 Thread Andreas Pakulat
On 19.06.07 21:42:05, Phil Thompson wrote: On Tuesday 19 June 2007 9:26 pm, Andreas Pakulat wrote: Hi, I just wanted to install eric4 and the first try to execute python install.py failed because QScintilla's qscintilla2.dll isn't installed into Qt's bin dir. It only is installed into

Re: [PyQt] QScintilla's dll is only install qt/lib on win32

2007-06-19 Thread Phil Thompson
On Tuesday 19 June 2007 11:26 pm, Andreas Pakulat wrote: On 19.06.07 21:42:05, Phil Thompson wrote: On Tuesday 19 June 2007 9:26 pm, Andreas Pakulat wrote: Hi, I just wanted to install eric4 and the first try to execute python install.py failed because QScintilla's qscintilla2.dll

Re: [PyQt] QScintilla's dll is only install qt/lib on win32

2007-06-19 Thread Andreas Pakulat
On 19.06.07 23:56:24, Phil Thompson wrote: On Tuesday 19 June 2007 11:26 pm, Andreas Pakulat wrote: BTW: would you mind having at least the install instructions in the README instead of an HTML file? I'm not maintaining two versions, especially as the README tells you were to find the