Re: [PyQt] Next Releases of PyQt and SIP
Phil Thompson wrote: Current PyQt and SIP snapshots have been switched back to the v4.6 and v4.9 maintenance branches and I've backported all bug fixes from the trunk. Please test these for any remaining regressions and, all being well, I'll make bug-fix releases later this week. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt -- We all know Linux is great...it does infinite loops in 5 seconds. Linus Torvalds -- Serge Montagnac http://www.obs-psr.com obs-...@orange.fr -- ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]
On Fri, 30 Oct 2009 23:06:56 -0600, Melton Low softw.d...@gmail.com
wrote:
On Tue, Oct 27, 2009 at 10:31 PM, Melton Low softw.d...@gmail.com
wrote:
On Wed, Oct 21, 2009 at 3:27 AM, Phil Thompson
p...@riverbankcomputing.com wrote:
On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low softw.d...@gmail.com
wrote:
On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson
p...@riverbankcomputing.com
wrote:
On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low
softw.d...@gmail.com
wrote:
Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to
produce
errors.
This is on a PPC Mac running OS X 10.4.11:
Python 2.6.3
Qt 4.5.3 carbon version
Sip 4.9.1 snapshots 20091015
PyQt4 4.6.1 snapshots 20091014
Configuration problem sharted with:
Qt 4.5.3 carbon version
Sip 4.9.1 snapshots 20091002
PyQt4 4.6.1 snapshots 20091002
Problem disappeared if I completely removed Qt and reinstalled an
earlier
version of Qt:
Qt 4.5.2 carbon version
Sip 4.9.1 snapshots 20091001
PyQt4 4.6.1 snapshots 20091001
I had posted the problem earlier. If this is being worked on,
please
ignore
this. In case the new configure verbose output is useful I am
including
it
as an attachment since it's quite lengthy.
Have you tried configuring SIP with --arch ppc?
Have you installed PyQt before on this system?
Phil
I have had PyQt on this system since of Qt 4.5.1.
I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day
before.
No
difference.
This looks like a problem with Qt v4.5.3 where it's insisting on
building
for i386 (even if you have CONFIG -= x86 in your .pro file).
It would be interesting to compare the contents of Qt's
mkspecs/features/mac directory with an earlier version of Qt. If they
are
different then this is what you would need to hack at.
You could also try adding CONFIG -= x86 to the top of the
qtdirs.profile
that PyQt's configure.py generates and run qmake manually on it to see
if
the -arch i386 still appears in the Makefile.
Phil
Hi Phil,
Just tried run qmake on qtdirs.mk manually with the added CONFIG line to
the top of qtdirs.pro. Please note that 'python configure.py --use-arch
ppc' did not complete but it did produce the qtdirs.pro and other qtdirs
files.
Attached are qtdirs.pro and the output of the qmake command. The first
g++
line showed -arch i386 and -arch ppc. Your suspicion may be correct.
Mel
Hi Phil,
I just downloaded the Mac Qt sources for 4.5.2 and 4.5.3. Two files in
the mkspecs/features/mac directory have changed namely default_post.prf
and
objective_c.prf.
The results running diff are as follow:
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
diff default_post.prf
~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac2a3,17
# Pick a suitable default architecture for qmake-based applications.
# If the Qt package contains one of x86 and x86_64, pick that one. If it
# contains both then use the compiler default. Make a similiar decision
for
# PowerPC-based systems. Note that this logic assumes that Qt has been
# configured with an architecture that is usable on the system.
qt:!isEmpty(QT_CONFIG) {
contains(QMAKE_HOST.arch, ppc) {
!contains(QT_CONFIG, ppc64):contains(QT_CONFIG, ppc):CONFIG +=
ppc
contains(QT_CONFIG, ppc64):!contains(QT_CONFIG, ppc):CONFIG +=
ppc64
} else {
!contains(QT_CONFIG, x86_64):contains(QT_CONFIG, x86):CONFIG +=
x86
contains(QT_CONFIG, x86_64):!contains(QT_CONFIG, x86):CONFIG +=
x86_64
}
}
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
diff objective_c.prf
~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac
3d2
isEmpty(QMAKE_OBJECTIVE_CFLAGS) { #bootstrap
12c11
}
---
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
I have attached the two files from 4.5.2 and 4.5.3. They have been
renamed
so you can tell from which Qt version it came from.
Hope you can figure out a fix.
This just confirms it's a Qt problem - or maybe you can build Qt in such a
way as to work around it - but I don't see how it is a PyQt problem.
Phil
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]
On Tue, Oct 27, 2009 at 10:31 PM, Melton Low softw.d...@gmail.com wrote:
On Wed, Oct 21, 2009 at 3:27 AM, Phil Thompson
p...@riverbankcomputing.com wrote:
On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low softw.d...@gmail.com
wrote:
On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson
p...@riverbankcomputing.com
wrote:
On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low softw.d...@gmail.com
wrote:
Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to
produce
errors.
This is on a PPC Mac running OS X 10.4.11:
Python 2.6.3
Qt 4.5.3 carbon version
Sip 4.9.1 snapshots 20091015
PyQt4 4.6.1 snapshots 20091014
Configuration problem sharted with:
Qt 4.5.3 carbon version
Sip 4.9.1 snapshots 20091002
PyQt4 4.6.1 snapshots 20091002
Problem disappeared if I completely removed Qt and reinstalled an
earlier
version of Qt:
Qt 4.5.2 carbon version
Sip 4.9.1 snapshots 20091001
PyQt4 4.6.1 snapshots 20091001
I had posted the problem earlier. If this is being worked on, please
ignore
this. In case the new configure verbose output is useful I am
including
it
as an attachment since it's quite lengthy.
Have you tried configuring SIP with --arch ppc?
Have you installed PyQt before on this system?
Phil
I have had PyQt on this system since of Qt 4.5.1.
I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day before.
No
difference.
This looks like a problem with Qt v4.5.3 where it's insisting on building
for i386 (even if you have CONFIG -= x86 in your .pro file).
It would be interesting to compare the contents of Qt's
mkspecs/features/mac directory with an earlier version of Qt. If they are
different then this is what you would need to hack at.
You could also try adding CONFIG -= x86 to the top of the qtdirs.profile
that PyQt's configure.py generates and run qmake manually on it to see if
the -arch i386 still appears in the Makefile.
Phil
Hi Phil,
Just tried run qmake on qtdirs.mk manually with the added CONFIG line to
the top of qtdirs.pro. Please note that 'python configure.py --use-arch
ppc' did not complete but it did produce the qtdirs.pro and other qtdirs
files.
Attached are qtdirs.pro and the output of the qmake command. The first g++
line showed -arch i386 and -arch ppc. Your suspicion may be correct.
Mel
Hi Phil,
I just downloaded the Mac Qt sources for 4.5.2 and 4.5.3. Two files in
the mkspecs/features/mac directory have changed namely default_post.prf and
objective_c.prf.
The results running diff are as follow:
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac melton$
diff default_post.prf
~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac2a3,17
# Pick a suitable default architecture for qmake-based applications.
# If the Qt package contains one of x86 and x86_64, pick that one. If it
# contains both then use the compiler default. Make a similiar decision
for
# PowerPC-based systems. Note that this logic assumes that Qt has been
# configured with an architecture that is usable on the system.
qt:!isEmpty(QT_CONFIG) {
contains(QMAKE_HOST.arch, ppc) {
!contains(QT_CONFIG, ppc64):contains(QT_CONFIG, ppc):CONFIG += ppc
contains(QT_CONFIG, ppc64):!contains(QT_CONFIG, ppc):CONFIG +=
ppc64
} else {
!contains(QT_CONFIG, x86_64):contains(QT_CONFIG, x86):CONFIG +=
x86
contains(QT_CONFIG, x86_64):!contains(QT_CONFIG, x86):CONFIG +=
x86_64
}
}
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac melton$
diff objective_c.prf
~/Desktop/qt/qt-mac-opensource-src-4.5.3/mkspecs/features/mac
3d2
isEmpty(QMAKE_OBJECTIVE_CFLAGS) { #bootstrap
12c11
}
---
BigMac:~/Desktop/qt/qt-mac-opensource-src-4.5.2/mkspecs/features/mac
melton$
I have attached the two files from 4.5.2 and 4.5.3. They have been renamed
so you can tell from which Qt version it came from.
Hope you can figure out a fix.
Mel
default_post.prf.4.5.2
Description: Binary data
objective_c.prf.4.5.2
Description: Binary data
default_post.prf.4.5.3
Description: Binary data
objective_c.prf.4.5.3
Description: Binary data
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]
On Wed, Oct 21, 2009 at 3:27 AM, Phil Thompson p...@riverbankcomputing.comwrote: On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low softw.d...@gmail.com wrote: On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson p...@riverbankcomputing.com wrote: On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low softw.d...@gmail.com wrote: Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. Have you tried configuring SIP with --arch ppc? Have you installed PyQt before on this system? Phil I have had PyQt on this system since of Qt 4.5.1. I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day before. No difference. This looks like a problem with Qt v4.5.3 where it's insisting on building for i386 (even if you have CONFIG -= x86 in your .pro file). It would be interesting to compare the contents of Qt's mkspecs/features/mac directory with an earlier version of Qt. If they are different then this is what you would need to hack at. You could also try adding CONFIG -= x86 to the top of the qtdirs.profile that PyQt's configure.py generates and run qmake manually on it to see if the -arch i386 still appears in the Makefile. Phil Hi Phil, Just tried run qmake on qtdirs.mk manually with the added CONFIG line to the top of qtdirs.pro. Please note that 'python configure.py --use-arch ppc' did not complete but it did produce the qtdirs.pro and other qtdirs files. Attached are qtdirs.pro and the output of the qmake command. The first g++ line showed -arch i386 and -arch ppc. Your suspicion may be correct. Mel BigMac:~/Downloads/PyQt-mac-gpl-4.6.1 melton$ make -f qtdirs.mk /usr/bin/qmake -spec /usr/local/Qt4.5/mkspecs/macx-g++ -macx -o qtdirs.mk qtdirs.pro g++ -headerpad_max_install_names -arch i386 -arch ppc -o qtdirs.app/Contents/MacOS/qtdirs qtdirs.o -F/Library/Frameworks -L/Library/Frameworks -framework QtCore -lz -lm -framework ApplicationServices /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: for architecture i386 /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libz.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libm.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/ApplicationServices.framework/ApplicationServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/libstdc++.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSystem.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /usr/lib/libz.1.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/libSystem.B.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/libstdc++.6.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning
Re: [PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]
Hi Phil, Sorry for the long delay. I am out of town and away from my PPC box. I will check out your suggestions when I get back early next week. I suspect there are more 10.5 Leopard and 10.6 Snow Leopard users than 10.4 Tiger users. If you need to do a release, we can deal with this later. I am writing this on a 10.6 Snow Leopard laptop which doesn't have the problem. I can live with the older versions on my PPC Tiger machine for awhile. Mel On Wed, Oct 21, 2009 at 3:27 AM, Phil Thompson p...@riverbankcomputing.comwrote: On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low softw.d...@gmail.com wrote: On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson p...@riverbankcomputing.com wrote: On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low softw.d...@gmail.com wrote: Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. Have you tried configuring SIP with --arch ppc? Have you installed PyQt before on this system? Phil I have had PyQt on this system since of Qt 4.5.1. I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day before. No difference. This looks like a problem with Qt v4.5.3 where it's insisting on building for i386 (even if you have CONFIG -= x86 in your .pro file). It would be interesting to compare the contents of Qt's mkspecs/features/mac directory with an earlier version of Qt. If they are different then this is what you would need to hack at. You could also try adding CONFIG -= x86 to the top of the qtdirs.profile that PyQt's configure.py generates and run qmake manually on it to see if the -arch i386 still appears in the Makefile. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP [Building on OS X 10.4]
On Tue, 20 Oct 2009 13:23:43 -0600, Melton Low softw.d...@gmail.com wrote: On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson p...@riverbankcomputing.com wrote: On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low softw.d...@gmail.com wrote: Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. Have you tried configuring SIP with --arch ppc? Have you installed PyQt before on this system? Phil I have had PyQt on this system since of Qt 4.5.1. I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day before. No difference. This looks like a problem with Qt v4.5.3 where it's insisting on building for i386 (even if you have CONFIG -= x86 in your .pro file). It would be interesting to compare the contents of Qt's mkspecs/features/mac directory with an earlier version of Qt. If they are different then this is what you would need to hack at. You could also try adding CONFIG -= x86 to the top of the qtdirs.pro file that PyQt's configure.py generates and run qmake manually on it to see if the -arch i386 still appears in the Makefile. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Fri, 16 Oct 2009 19:42:20 +0200, Giovanni Bajo ra...@develer.com wrote: On 10/16/2009 3:38 PM, Phil Thompson wrote: On Fri, 16 Oct 2009 15:31:08 +0200, Giovanni Bajo ra...@develer.com wrote: On 10/16/2009 10:10 AM, Phil Thompson wrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week. BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Hi Phil, I got some GC-related random crashes in a testsuite run after you fixed the QApplication destruction. I investigated them enough to see that it's related to invokation of focusPolicy() or other focus-related virtual methods on an already-deleted object, but they are hard to track down and I am not sure whenever I will have a reproduction recipe ready. Is there anything specific to focus stuff that rings a bell to you? No. The obvious source of the problem is the QApplication being deleted too soon in relation to some other object. I delete all top-level widgets, flush all the events (qApp.processEvents()), and run an explicit gc.collect() pass. I actually don't know what else to do... I start to believe that it's a Qt problem rather than a PyQt's one; eg: some globals somewhere in the focus code that is not reset by QApplication's destructor and still points to some destroyed object. I'll have a further look. Any progress? I'd prefer to revert to the existing broken behaviour (which affects almost nobody) than introduce the potential for random crash-on-exit bugs. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Tue, 2009-10-20 at 09:41 +0100, Phil Thompson wrote: On Fri, 16 Oct 2009 19:42:20 +0200, Giovanni Bajo ra...@develer.com wrote: On 10/16/2009 3:38 PM, Phil Thompson wrote: On Fri, 16 Oct 2009 15:31:08 +0200, Giovanni Bajo ra...@develer.com wrote: On 10/16/2009 10:10 AM, Phil Thompson wrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week. BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Hi Phil, I got some GC-related random crashes in a testsuite run after you fixed the QApplication destruction. I investigated them enough to see that it's related to invokation of focusPolicy() or other focus-related virtual methods on an already-deleted object, but they are hard to track down and I am not sure whenever I will have a reproduction recipe ready. Is there anything specific to focus stuff that rings a bell to you? No. The obvious source of the problem is the QApplication being deleted too soon in relation to some other object. I delete all top-level widgets, flush all the events (qApp.processEvents()), and run an explicit gc.collect() pass. I actually don't know what else to do... I start to believe that it's a Qt problem rather than a PyQt's one; eg: some globals somewhere in the focus code that is not reset by QApplication's destructor and still points to some destroyed object. I'll have a further look. Any progress? I'd prefer to revert to the existing broken behaviour (which affects almost nobody) than introduce the potential for random crash-on-exit bugs. Sorry, no progress at this time. If you revert it, please send me the patch so that I can test it by myself and let you know when I have some progress. -- Giovanni Bajo Develer S.r.l. http://www.develer.com ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Tue, Oct 20, 2009 at 11:17 AM, Phil Thompson p...@riverbankcomputing.com wrote: On Sat, 17 Oct 2009 17:31:40 -0600, Melton Low softw.d...@gmail.com wrote: Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. Have you tried configuring SIP with --arch ppc? Have you installed PyQt before on this system? Phil I have had PyQt on this system since of Qt 4.5.1. I tried --arch=PPC with Sip and --use_arch=PPC with PyQt the day before. No difference. I also tried using the uninstall-qt.py script to remove Qt. I did find something different when using the installed uninstall-qt.py script under Qt 4.5.2 vs Qt 4.5.3. Under Qt 4.5.2, eveything in /Library/Frameworks got removed. Under Qt 4.5.3, the /Library/Frameworks/QtCore.framework was left behind. I don't know if this mean anything. Mel ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
Am Sonntag 18 Oktober 2009 schrieb Melton Low: Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. That line looks suspicious: g++ -c -pipe -g -gdwarf-2 -arch i386 -Wall -W -DQT_CORE_LIB -DQT_SHARED -I/usr/local/Qt4.5/mkspecs/macx-g++ -I. -I/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/usr/include/QtCore -I/usr/include -I. -F/Library/Frameworks -o qtdirs.o qtdirs.cpp It looks like it is confused about two Qt installations. Remove one and try again. Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
Executing PyQt4's configure.py on Mac OS X 10.4.11 continues to produce errors. This is on a PPC Mac running OS X 10.4.11: Python 2.6.3 Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091015 PyQt4 4.6.1 snapshots 20091014 Configuration problem sharted with: Qt 4.5.3 carbon version Sip 4.9.1 snapshots 20091002 PyQt4 4.6.1 snapshots 20091002 Problem disappeared if I completely removed Qt and reinstalled an earlier version of Qt: Qt 4.5.2 carbon version Sip 4.9.1 snapshots 20091001 PyQt4 4.6.1 snapshots 20091001 I had posted the problem earlier. If this is being worked on, please ignore this. In case the new configure verbose output is useful I am including it as an attachment since it's quite lengthy. Mel On Fri, Oct 16, 2009 at 2:10 AM, Phil Thompson p...@riverbankcomputing.comwrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week. BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt Last login: Sat Oct 17 17:12:58 on ttyp1 Welcome to Darwin! BigMac:~ melton$ cd Downloads/PyQt-mac-gpl-4.6.1-snapshot-20091014 BigMac:~/Downloads/PyQt-mac-gpl-4.6.1-snapshot-20091014 melton$ python configure.py Determining the layout of your Qt installation... Error: Failed to determine the layout of your Qt installation. Try again using the --verbose flag to see more detail about the problem. BigMac:~/Downloads/PyQt-mac-gpl-4.6.1-snapshot-20091014 melton$ python configure.py --verbose Determining the layout of your Qt installation... /usr/bin/qmake -spec macx-g++ -o qtdirs.mk qtdirs.pro make -f qtdirs.mk g++ -c -pipe -g -gdwarf-2 -arch i386 -Wall -W -DQT_CORE_LIB -DQT_SHARED -I/usr/local/Qt4.5/mkspecs/macx-g++ -I. -I/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/usr/include/QtCore -I/usr/include -I. -F/Library/Frameworks -o qtdirs.o qtdirs.cpp g++ -headerpad_max_install_names -arch i386 -o qtdirs.app/Contents/MacOS/qtdirs qtdirs.o -F/Library/Frameworks -L/Library/Frameworks -framework QtCore -lz -lm -framework ApplicationServices /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libz.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libm.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/ApplicationServices.framework/ApplicationServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/libstdc++.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSystem.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /usr/lib/libz.1.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/libSystem.B.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning fat file: /usr/lib/libstdc++.6.dylib does not contain an architecture that matches the specified -arch flag: i386 (file ignored) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: warning /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols: ___keymgr_dwarf2_register_sections __cthread_init_routine _errno _exit _mach_init_routine __keymgr_get_and_lock_processwide_ptr __keymgr_get_and_lock_processwide_ptr_2 __keymgr_set_and_unlock_processwide_ptr _calloc _dlopen _dlsym _free _malloc
Re: [PyQt] Next Releases of PyQt and SIP
On Fri, Oct 16, 2009 at 11:10 AM, Phil Thompson p...@riverbankcomputing.com wrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. So this one should be fixed now: https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/452453 http://www.mail-archive.com/pyqt@riverbankcomputing.com/msg19157.html ? -- Ville M. Vainio http://tinyurl.com/vainio ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
To reproduce.
class _Base:
def foo(self):
self.setWindowTitle('foo')
class MyWindow(QWindow, _Base):
def __init__(self):
QWindow.__init__(self)
self.setWindowTitle()
To avoid segfault:
class _Base(object):
Can't PyQt detect multiple inheritance from old-style class?
--
Naoki INADA songofaca...@gmail.com
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Fri, 16 Oct 2009 17:51:21 +0900, INADA Naoki songofaca...@gmail.com
wrote:
To reproduce.
class _Base:
def foo(self):
self.setWindowTitle('foo')
class MyWindow(QWindow, _Base):
def __init__(self):
QWindow.__init__(self)
self.setWindowTitle()
To avoid segfault:
class _Base(object):
Can't PyQt detect multiple inheritance from old-style class?
As I said, all bug reports have been fixed. However the point is for you to
prove it for yourself by testing with the current snapshots.
Phil
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
Am Freitag 16 Oktober 2009 schrieb Phil Thompson: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. Unfortunately, I've crashed eric again with current snapshots as available on: http://download.opensuse.org/repositories/home:/frispete:/branches:/KDE:/KDE4:/Factory:/Desktop/ To be exact, it's sip-4.9.1-snapshot-20091014.tar.gz + yesterdays fix, PyQt-x11-gpl-4.6.1-snapshot-20091014.tar.gz, eric 4.3.8, and pysvn 1.7.0. The whole suite is build against Qt-4.5.3 now. Again, I've committed a newly added directory (8 binary files with a total of 6kb) in a small project. On the commit confirmation dialog, I hit close immediately, when it turned enabled, which triggers the crash. This is pretty reliably reproducible that way. Starting program: /usr/bin/python /usr/lib/python2.6/site-packages/eric4/eric4.py [Thread debugging using libthread_db enabled] [New Thread 0xb3a2ab90 (LWP 27336)] [New Thread 0xb320fb90 (LWP 27365)] [New Thread 0xb2a0eb90 (LWP 27366)] [New Thread 0xb220db90 (LWP 27367)] [Thread 0xb220db90 (LWP 27367) exited] [Thread 0xb2a0eb90 (LWP 27366) exited] [New Thread 0xb220db90 (LWP 27373)] [New Thread 0xb2a0eb90 (LWP 27374)] [Thread 0xb2a0eb90 (LWP 27374) exited] [Thread 0xb220db90 (LWP 27373) exited] [New Thread 0xb2a0eb90 (LWP 27375)] [Thread 0xb2a0eb90 (LWP 27375) exited] [New Thread 0xb2a0eb90 (LWP 27376)] [Thread 0xb2a0eb90 (LWP 27376) exited] [New Thread 0xb2a0eb90 (LWP 27377)] Program received signal SIGSEGV, Segmentation fault. 0xb7885585 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/libQtCore.so.4 (gdb) bt #0 0xb7885585 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/libQtCore.so.4 #1 0xb788586c in QCoreApplication::postEvent(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #2 0xb7895127 in QObject::deleteLater() () from /usr/lib/libQtCore.so.4 #3 0xb7b1cf70 in PyQtProxy::unislot (this=0xaa21bf8, qargs=0xa9ee398) at qpycore_pyqtproxy.cpp:384 #4 0xb7b1d085 in PyQtProxy::qt_metacall (this=0xaa21bf8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa9ee398) at qpycore_pyqtproxy.cpp:344 #5 0xb789aee8 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #6 0xb7b23174 in qpycore_emit (qtx=0xaa21a88, signal_index=5, parsed_signature=0xb3b5460, sigargs=0xb7c5602c) at qpycore_sip_helpers.cpp:422 #7 0xb7b23b28 in qpycore_qobject_emit (qtx=0xaa21a88, sig=0x8303e1c 2accepted(), sigargs=0xb7c5602c) at qpycore_sip_helpers.cpp:358 #8 0xb7b0b33b in meth_QObject_emit (sipSelf=0xaad65ac, sipArgs=0x831146c) at sip/QtCore/qobject.sip:409 #9 0xb7ea4875 in PyCFunction_Call (func=0x82fb2ac, arg=0x831146c, kw=0x0) at Objects/methodobject.c:81 #10 0xb7ef7485 in PyEval_EvalFrameEx (f=0xb3180fc, throwflag=0) at Python/ceval.c:3679 #11 0xb7efcb9b in PyEval_EvalCodeEx (co=0xa39b458, globals=0xa320b54, locals=0x0, args=0x8311498, argcount=1, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2942 #12 0xb7e91a29 in function_call (func=0xa39aa04, arg=0x831148c, kw=0x0) at Objects/funcobject.c:524 #13 0xb7e6cc1c in PyObject_Call (func=0xa39aa04, arg=0x831148c, kw=0x0) at Objects/abstract.c:2487 #14 0xb7e7a9fe in instancemethod_call (func=0xa39aa04, arg=0x831148c, kw=0x0) at Objects/classobject.c:2579 #15 0xb7e6cc1c in PyObject_Call (func=0xa37557c, arg=0xb7c5602c, kw=0x0) at Objects/abstract.c:2487 #16 0xb7ef574f in PyEval_CallObjectWithKeywords (func=0xa37557c, arg=0xb7c5602c, kw=0x0) at Python/ceval.c:3548 #17 0xb79a86cf in sip_api_invoke_slot (slot=0xaa1ba64, sigargs=0xb7c5602c) at qtlib.c:191 #18 0xb7b1ce5b in PyQtProxy::invokeSlot (sl...@0xaa1ba64, qargs=0xbfffc1d8) at qpycore_pyqtproxy.cpp:426 #19 0xb7b1cf55 in PyQtProxy::unislot (this=0xaa1ba48, qargs=0xbfffc1d8) at qpycore_pyqtproxy.cpp:379 #20 0xb7b1d085 in PyQtProxy::qt_metacall (this=0xaa1ba48, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfffc1d8) at qpycore_pyqtproxy.cpp:344 #21 0xb789aee8 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb789bb72 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #23 0xb6627ed7 in QDialogButtonBox::accepted() () from /usr/lib/libQtGui.so.4 #24 0xb6628168 in ?? () from /usr/lib/libQtGui.so.4 #25 0xb662a086 in QDialogButtonBox::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtGui.so.4 #26 0xb712907a in sipQDialogButtonBox::qt_metacall (this=0xaa14030, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbfffc39c) at sipQtGuiQDialogButtonBox.cpp:386 #27 0xb789aee8 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #28 0xb789b320 in QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4 #29 0xb68ccb71 in QAbstractButton::clicked(bool) () from /usr/lib/libQtGui.so.4 #30 0xb65f4459 in ?? () from /usr/lib/libQtGui.so.4
RE: [PyQt] Next Releases of PyQt and SIP
BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Phil Wow, that's great! Is Animation framework and state machine supported? Can't wait to test those c00l animations! :) pyqt 4.6.1. on next week will be build against qt 4.6 beta or qt 4.5? I would like to port couple of new animation demos to pyqt! Could I have an exe installer please? --- Igor igor at tyumbit.ru ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
RE: [PyQt] Next Releases of PyQt and SIP
On Fri, 16 Oct 2009 16:34:12 +0600, Igor Prischepoff i...@tyumbit.ru wrote: BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Phil Wow, that's great! Is Animation framework and state machine supported? Can't wait to test those c00l animations! :) pyqt 4.6.1. on next week will be build against qt 4.6 beta or qt 4.5? I would like to port couple of new animation demos to pyqt! Could I have an exe installer please? I said it built against the beta, I didn't say it supported the new features of the beta. That support will be added when Qt v4.6 is released. All I've done is work around the incompatibilities introduced in the beta. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On 10/16/2009 10:10 AM, Phil Thompson wrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week. BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Hi Phil, I got some GC-related random crashes in a testsuite run after you fixed the QApplication destruction. I investigated them enough to see that it's related to invokation of focusPolicy() or other focus-related virtual methods on an already-deleted object, but they are hard to track down and I am not sure whenever I will have a reproduction recipe ready. Is there anything specific to focus stuff that rings a bell to you? -- Giovanni Bajo Develer S.r.l. http://www.develer.com ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Fri, 16 Oct 2009 15:31:08 +0200, Giovanni Bajo ra...@develer.com wrote: On 10/16/2009 10:10 AM, Phil Thompson wrote: All outstanding bug reports against PyQt and SIP have been resolved - if you disagree then let me know. I plan to release PyQt v4.6.1 and SIP v4.9.1 early next week. BTW, the current PyQt snapshot will build against Qt v4.6-beta1. Hi Phil, I got some GC-related random crashes in a testsuite run after you fixed the QApplication destruction. I investigated them enough to see that it's related to invokation of focusPolicy() or other focus-related virtual methods on an already-deleted object, but they are hard to track down and I am not sure whenever I will have a reproduction recipe ready. Is there anything specific to focus stuff that rings a bell to you? No. The obvious source of the problem is the QApplication being deleted too soon in relation to some other object. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Mon, 07 Sep 2009 20:44:13 -0400, Matt Smith mel...@orangepalantir.org wrote: The long and short, when I use a QThread at the end of my run method, I call self.deleteLater(). If I call self.deleteLater() the finished() signal is never emitted. It used to emit finished() even if I called deletLate(), and I thought I needed the self.deleteLater() to clean up connections and such. If interested I could easily post an example. If not Ill emit finished() before the delete later. I would need a test case, and to know which versions you are talking about. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
Here is a minimal test case, which works fine my computer at work: windows xp, and the current release of PyQt with python 2.6. This script is very similar to the one I have at home, and I expect that it would fail, but I haven't seen this script fail so Ill try it at home this afternoon. If it fails Ill try a newer snapshot. mbs from PyQt4 import QtGui,QtCore import sys class WhenDeleted(QtCore.QThread): def __init__(self,app,parent=None): QtCore.QThread.__init__(self,parent) self.connect(self,QtCore.SIGNAL(finished()),self.echo) self.connect(self,QtCore.SIGNAL(started()),self.stop) def run(self): self.exec_() print finished here self.deleteLater() def stop(self): self.quit(); def echo(self): print Recieved finished() signal app.quit() if __name__==__main__: app = QtGui.QApplication(sys.argv) x = WhenDeleted(app) x.start() sys.exit(app.exec_()) On Mon, 07 Sep 2009 20:44:13 -0400, Matt Smith mel...@orangepalantir.org wrote: The long and short, when I use a QThread at the end of my run method, I call self.deleteLater(). If I call self.deleteLater() the finished() signal is never emitted. It used to emit finished() even if I called deletLate(), and I thought I needed the self.deleteLater() to clean up connections and such. If interested I could easily post an example. If not Ill emit finished() before the delete later. I would need a test case, and to know which versions you are talking about. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
I am at home using the most recent version of pyqt and sip (20090906) that I compiled on linux amd64. I am using Qt 4.5.0 that comes with ubuntu 9.04. The example that I sent does not work because the finished() never gets emitted if I include the 'deleteLater' call. I do not have dbus if that makes a difference. mbs On Tue, 2009-09-08 at 08:15 +0100, Phil Thompson wrote: On Mon, 07 Sep 2009 20:44:13 -0400, Matt Smith mel...@orangepalantir.org wrote: The long and short, when I use a QThread at the end of my run method, I call self.deleteLater(). If I call self.deleteLater() the finished() signal is never emitted. It used to emit finished() even if I called deletLate(), and I thought I needed the self.deleteLater() to clean up connections and such. If interested I could easily post an example. If not Ill emit finished() before the delete later. I would need a test case, and to know which versions you are talking about. Phil #!/usr/bin/env python from PyQt4 import QtGui,QtCore import sys class WhenDeleted(QtCore.QThread): def __init__(self,app,parent=None): QtCore.QThread.__init__(self,parent) self.connect(self,QtCore.SIGNAL(finished()),self.echo) self.connect(self,QtCore.SIGNAL(started()),self.stop) def run(self): self.exec_() print finished here self.deleteLater() #comment out this line and it works def stop(self): self.quit(); def echo(self): print Recieved finished() signal app.quit() if __name__==__main__: app = QtGui.QApplication(sys.argv) x = WhenDeleted(app) x.start() sys.exit(app.exec_()) ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Tue, 08 Sep 2009 10:37:36 -0400, Matt Smith mel...@orangepalantir.org wrote: I am at home using the most recent version of pyqt and sip (20090906) that I compiled on linux amd64. I am using Qt 4.5.0 that comes with ubuntu 9.04. The example that I sent does not work because the finished() never gets emitted if I include the 'deleteLater' call. I do not have dbus if that makes a difference. mbs It will work if you add QtCore.Qt.DirectConnection to the connect of the finish() signal. A change in the current snapshot is that the proxy that wraps a Python callable to receive a signal is deleted sooner (ie. it doesn't use deleteLater() any more). I'm guessing that this means that it's now being deleted in the same iteration of the event loop that is deleting the thread. However, this shouldn't matter as (I think) the finished() signal should be delivered synchronously and not queued as it appears to be doing. The Qt code that decides whether or not to queue the signal is a bit obscure - it doesn't do the obvious things of comparing thread ids. Phil On Tue, 2009-09-08 at 08:15 +0100, Phil Thompson wrote: On Mon, 07 Sep 2009 20:44:13 -0400, Matt Smith mel...@orangepalantir.org wrote: The long and short, when I use a QThread at the end of my run method, I call self.deleteLater(). If I call self.deleteLater() the finished() signal is never emitted. It used to emit finished() even if I called deletLate(), and I thought I needed the self.deleteLater() to clean up connections and such. If interested I could easily post an example. If not Ill emit finished() before the delete later. I would need a test case, and to know which versions you are talking about. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP
On Mon, 07 Sep 2009 09:08:27 +0100
Phil Thompson p...@riverbankcomputing.com wrote:
The current snapshots of PyQt4 and SIP should be considered release
candidates, so now would be a good time to test against them.
The only outstanding problem I am aware of is the build problems on
Snow Leopard - and I'm still waiting for my upgrade from Apple before
I can fix that.
When trying to build a deprecated version of PyQwt (for Qt-3 and a
version of Qwt incompatible with Qt-4), I ran into the following:
sipQwtpart0.cpp: In function ‘PyObject*
meth_QwtPlot_curveIterator(PyObject*, PyObject*)’:
sipQwtpart0.cpp:46123: error: cannot convert ‘QwtPlotCurveIterator’ to
‘QwtPlotCurveIterator*’ in assignment
where the generated code reads:
extern C {static PyObject *meth_QwtPlot_curveIterator(PyObject *,
PyObject *);}
static PyObject *meth_QwtPlot_curveIterator(PyObject *sipSelf, PyObject
*sipArgs)
{
int sipArgsParsed = 0;
{
QwtPlot *sipCpp;
if
(sipParseArgs(sipArgsParsed,sipArgs,B,sipSelf,sipType_QwtPlot,sipCpp))
{
QwtPlotCurveIterator *sipRes;
sipRes = sipCpp-curveIterator(); // *ERROR IN ASSIGNMENT*
return
sipConvertFromType(sipRes,sipType_QwtPlotCurveIterator,NULL);
}
}
/* Raise an exception if the arguments couldn't be parsed. */
sipNoMethod(sipArgsParsed,sipName_QwtPlot,sipName_curveIterator);
return NULL;
}
A snippet from the sip file is:
class QwtPlot: QFrame
{
%TypeHeaderCode
#include qwt_plot.h
%End // %TypeHeaderCode
public:
...
QwtPlotCurveIterator curveIterator() const;
...
}; // class QwtPlot
where QwtPlotCurveIterator is a class defined by Qwt and also having a
SIP specification.
This problem is present with the latest SIP-snapshot but also with
SIP-4.8.2.
Regards -- Gerard
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Next Releases of PyQt and SIP and Updated Windows Installer
On Thu, Jun 12, 2008 at 7:29 AM, Phil Thompson [EMAIL PROTECTED] wrote: PyQt v4.4.3 and SIP v4.7.7 should be released some time over the next week. The emphasis is on fixing regressions and pyuic4 catching up with the changes in Qt v4.4. Hi Phil, Did you get a chance to look at my sip bug/patch I posted about last week? I just tried the latest snapshots and I ran into the segfault again. In case the mail server ate the email, it's here: http://article.gmane.org/gmane.comp.python.pyqt-pykde/12295 ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
