[PyQt] ANN: PyQt v4.6.2 and SIP v4.9.2 Released

2009-11-20 Thread Phil Thompson
PyQt v4.6.2 and SIP v4.9.2 have been released and can be downloaded from
the usual places.

These are both bug-fix releases.

Phil
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt


Re: [PyQt] INSTALL_ROOT DESTDIR

2009-11-20 Thread jong357



jong357 wrote:
 
 Just a heads up, looks like the designer directory in PyQt-x11-gpl-4.6.1
 uses INSTALL_ROOT instead of DESTDIR like the rest of the source seems to
 use. When packaging, this spams the system, albiet fairly minor. Didn't
 bother to track down what qmake was doing but I assume the problem lies
 there.
 
 I'm just using both targets on the make install until this is fixed
 upstream. Sorry I didn't troubleshoot and send a patch 
 

Still does it... I realize this isn't a show stopper issue but spamming the
host system is a little on the rude side IMO. ;-)

make[1]: Entering directory `/tmp/PyQt-x11-gpl-4.6.2/designer'
install -m 755 -p libpythonplugin.so
/usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
strip --strip-unneeded
/usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
cp -f -r /tmp/PyQt-x11-gpl-4.6.2/designer/python
/usr/lib/qt-4.5.3/plugins/designer/
make[1]: Leaving directory `/tmp/PyQt-x11-gpl-4.6.2/designer'

-- 
View this message in context: 
http://old.nabble.com/INSTALL_ROOT---DESTDIR-tp26219346p26441576.html
Sent from the PyQt mailing list archive at Nabble.com.

___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt


Re: [PyQt] INSTALL_ROOT DESTDIR

2009-11-20 Thread Phil Thompson
On Fri, 20 Nov 2009 05:21:59 -0800 (PST), jong357 jgrossh...@gmail.com
wrote:
 jong357 wrote:
 
 Just a heads up, looks like the designer directory in PyQt-x11-gpl-4.6.1
 uses INSTALL_ROOT instead of DESTDIR like the rest of the source seems
to
 use. When packaging, this spams the system, albiet fairly minor. Didn't
 bother to track down what qmake was doing but I assume the problem lies
 there.
 
 I'm just using both targets on the make install until this is fixed
 upstream. Sorry I didn't troubleshoot and send a patch 
 
 
 Still does it... I realize this isn't a show stopper issue but spamming
the
 host system is a little on the rude side IMO. ;-)
 
 make[1]: Entering directory `/tmp/PyQt-x11-gpl-4.6.2/designer'
 install -m 755 -p libpythonplugin.so
 /usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
 strip --strip-unneeded
 /usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
 cp -f -r /tmp/PyQt-x11-gpl-4.6.2/designer/python
 /usr/lib/qt-4.5.3/plugins/designer/
 make[1]: Leaving directory `/tmp/PyQt-x11-gpl-4.6.2/designer'

It's put in the directory that Designer expects to find it. If you want to
put it somewhere else use the -p flag to configure.py.

Phil
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt


Re: [PyQt] INSTALL_ROOT DESTDIR

2009-11-20 Thread Jon Grosshart
On Fri, Nov 20, 2009 at 8:45 AM, Phil Thompson
p...@riverbankcomputing.comwrote:

 On Fri, 20 Nov 2009 05:21:59 -0800 (PST), jong357 jgrossh...@gmail.com
 wrote:
  jong357 wrote:
 
  Just a heads up, looks like the designer directory in PyQt-x11-gpl-4.6.1
  uses INSTALL_ROOT instead of DESTDIR like the rest of the source seems
 to
  use. When packaging, this spams the system, albiet fairly minor. Didn't
  bother to track down what qmake was doing but I assume the problem lies
  there.
 
  I'm just using both targets on the make install until this is fixed
  upstream. Sorry I didn't troubleshoot and send a patch
 
 
  Still does it... I realize this isn't a show stopper issue but spamming
 the
  host system is a little on the rude side IMO. ;-)
 
  make[1]: Entering directory `/tmp/PyQt-x11-gpl-4.6.2/designer'
  install -m 755 -p libpythonplugin.so
  /usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
  strip --strip-unneeded
  /usr/lib/qt-4.5.3/plugins/designer/libpythonplugin.so
  cp -f -r /tmp/PyQt-x11-gpl-4.6.2/designer/python
  /usr/lib/qt-4.5.3/plugins/designer/
  make[1]: Leaving directory `/tmp/PyQt-x11-gpl-4.6.2/designer'

 It's put in the directory that Designer expects to find it. If you want to
 put it somewhere else use the -p flag to configure.py.

 Phil


I think you've missed the point. When I specify:

make install DESTDIR=/some/place

I expect said software to install to /some/place, not spam my host system
with where it should go and to completely ignore DESTDIR As far as I'm
aware, the designer directory is the only one that does this. It uses
INSTALL_ROOT instead of DESTDIR

This is a problem from a packagers standpoint and should be addressed.

Jon
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt

Re: [PyQt] Problem with class inheriting QDialog

2009-11-20 Thread David Douard
Looks like you are not calling QMainWindow base constructor.


Le Friday 20 November 2009 17:44:30 dizou, vous avez écrit :
 Dialog.py:

 import sys
 from PyQt4.QtGui import QDialog

 def Dialog(QDialog):
   def __init__(self, parent):
   QDialog.__init__(self, parent)

 MainWindow.py:

 from PyQt4.QtCore import SIGNAL, SLOT, QDir, QFile
 from PyQt4.QtGui import QApplication, QMainWindow, QMenu, QMessageBox, \
  QWidget, qApp, QAction, QFileDialog, QPushButton
 from Dialog import *

 class MainWindow(QMainWindow):
 def __init__(self):

  QMainWindow.__init__(self)

 #stuff
 self.editButton = QPushButton(self)
 self.connect(self.editButton, SIGNAL(clicked()),
 self.EditButtonClicked)
 def EditButtonClicked(self):
 self.dialog = Dialog(self)
 print type(self.dialog)
 self.dialog.exec_()



-- 
David DouardLOGILAB, Paris (France), +33 1 45 32 03 12
Formations Python, Zope, Debian :   http://www.logilab.fr/formations
Développement logiciel sur mesure : http://www.logilab.fr/services
Informatique scientifique : http://www.logilab.fr/science

___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt


Re: [PyQt] Freezes and crashes with signal autoconnection

2009-11-20 Thread Christian Roche

Hi Phil,


Phil Thompson-5 wrote:
 
 I thought you were using current snapshots (where the code that was
 crashing was only compiled in with old versions of Qt).
 

I've just tried against the latest snapshots
(sip-4.9.2-snapshot-20091115.tar.gz and 
PyQt-x11-gpl-4.6.2-snapshot-20091115.tar.gz) however the results are even
worse; the application crashes very quickly with the following trace. I
suspect it might be related to the installation, however the demos seem to
work ok.
-
Program terminated with signal 11, Segmentation fault.  
  
#0  memcpy () at ../sysdeps/i386/i686/memcpy.S:75
in ../sysdeps/i386/i686/memcpy.S
Missing separate debuginfos, use: debuginfo-install
OpenEXR-libs-1.6.1-8.fc11.i586 e2fsprogs-libs-1.41.4-12.fc11.i586
fontconfig-2.7.1-1.fc11.i586 freetype-2.3.9-5.fc11.i586
ilmbase-1.0.1-4.fc11.i586 jasper-libs-1.900.1-13.fc11.i586
kdelibs-4.3.2-4.fc11.i586 keyutils-libs-1.2-5.fc11.i586
krb5-libs-1.6.3-20.fc11.i586 lcms-libs-1.18-2.fc11.i586
libICE-1.0.4-7.fc11.i586 libSM-1.1.0-4.fc11.i586 libXau-1.0.4-5.fc11.i586
libXcursor-1.1.9-4.fc11.i586 libXdamage-1.1.1-6.fc11.i586
libXfixes-4.0.3-5.fc11.i586 libXi-1.2.1-1.fc11.i586
libXinerama-1.0.3-4.fc11.i586 libXrandr-1.2.99.4-3.fc11.i586
libXrender-0.9.4-5.fc11.i586 libXxf86vm-1.0.2-2.fc11.i586
libattr-2.4.43-3.fc11.i586 libcap-2.16-4.fc11.1.i586
libdrm-2.4.11-2.fc11.i586 libgcrypt-1.4.4-6.fc11.i586
libgpg-error-1.6-3.i586 libjpeg-6b-45.fc11.i586 libmng-1.0.10-2.fc11.i586
libpng-1.2.37-1.fc11.i586 libselinux-2.0.80-1.fc11.i586
libtiff-3.8.2-14.fc11.i586 libxcb-1.2-4.fc11.i586
linuxwacom-0.8.2.2-11.fc11.i586 phonon-4.3.1-102.fc11.i586
qt-x11-4.5.3-9.fc11.i586 xz-libs-4.999.9-0.1.beta.20091007git.fc11.i586
(gdb) bt
#0  memcpy () at ../sysdeps/i386/i686/memcpy.S:75
#1  0xb66020d8 in ?? ()
#2  0x01a0b7a7 in QString::append (this=0xb6621000, s...@0x9ee9490) at
/usr/include/bits/string3.h:52
#3  0x04506e8d in QString::operator+= (s=value optimized out, this=value
optimized out)
at ../../src/corelib/tools/qstring.h:269
#4  QTextCursor::insertText (s=value optimized out, this=value optimized
out)
at text/qtextcursor.cpp:1307
#5  0x04507312 in QTextCursor::insertText (this=0xbfeac73c,
te...@0xb66020d8) at text/qtextcursor.cpp:1275
#6  0x04499c71 in QTextControlPrivate::append (this=0x9d4ead0,
te...@0xb66020d8, format=Qt::AutoText)
at text/qtextcontrol.cpp:2740
#7  0x04499dd3 in QTextControl::append (this=0x9d4eac0, te...@0xb66020d8) at
text/qtextcontrol.cpp:2754
#8  0x04702459 in QTextEdit::append (this=0x9d4d4f0, te...@0xb66020d8) at
widgets/qtextedit.cpp:2597
#9  0x011e3149 in meth_QTextEdit_append (sipSelf=0x9bdd3ac,
sipArgs=0x9bdebcc) at sipQtGuiQTextEdit.cpp:3381
#10 0x03641762 in PyCFunction_Call (func=0x9be5fcc, arg=0x9bdebcc, kw=0x0)
at Objects/methodobject.c:81
#11 0x0369d5be in call_function (oparg=value optimized out,
pp_stack=value optimized out)
at Python/ceval.c:3679
#12 PyEval_EvalFrameEx (oparg=value optimized out, pp_stack=value
optimized out) at Python/ceval.c:2370
#13 0x0369ed79 in PyEval_EvalCodeEx (co=0xb781aad0, globals=0xb786e02c,
locals=0x0, args=0x9b7d078,
argcount=2, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at
Python/ceval.c:2942
#14 0x0362db87 in function_call (func=0x9be2294, arg=0x9b7d06c, kw=0x0) at
Objects/funcobject.c:524
#15 0x0360172c in PyObject_Call (func=0x9be2294, arg=0x9b7d06c, kw=0x0) at
Objects/abstract.c:2487
#16 0x03617284 in instancemethod_call (func=0xb73b189c, arg=0x9b7d06c,
kw=0x0) at Objects/classobject.c:2579
#17 0x0360172c in PyObject_Call (func=0xb73b189c, arg=0x9bdeb4c, kw=0x0) at
Objects/abstract.c:2487
#18 0x03697f14 in PyEval_CallObjectWithKeywords (func=0xb73b189c,
arg=0x9bdeb4c, kw=0x0)
at Python/ceval.c:3548
#19 0x003ba2ff in ?? () from /usr/lib/python2.6/site-packages/sip.so
#20 0xb73b189c in ?? ()
#21 0x09bdeb4c in ?? ()
#22 0x in ?? ()
Current language:  auto; currently asm
-
-- 
View this message in context: 
http://old.nabble.com/Freezes-and-crashes-with-signal-autoconnection-tp25716493p2667.html
Sent from the PyQt mailing list archive at Nabble.com.

___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt


[PyQt] Rich text in buttons

2009-11-20 Thread Richard A. Litherland
I'm very new to this, so I apologize if this question has been asked 1000 
times before. The text property of QAbstractButton doesn't recognize HTML 
markup, but the developers of KCalc, at least, have managed to work around 
this. I can't figure out how. Does anybody know?


Rick L.
--
R.A. Litherland: lit...@math.lsu.edu
Web page: http://www.math.lsu.edu/~lither/
Other web page: http://www.orangeclawhammer.net/
Charity is a cold grey loveless thing. -- Clement Attlee
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt