[PyQt] Build problem with latest PyQt snapshot on Windows
fined reference to `_imp__qpycore_pyqtSignal_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_post_init.o):qpycore_po st_init.cpp:(.text+0xb5): undefined reference to `_imp__qpycore_pyqtSignal_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_post_init.o):qpycore_po st_init.cpp:(.text+0xdc): undefined reference to `_imp__qpycore_pyqtBoundSignal_ Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_post_init.o):qpycore_po st_init.cpp:(.text+0xed): undefined reference to `_imp__qpycore_pyqtBoundSignal_ Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_post_init.o):qpycore_po st_init.cpp:(.text+0x269): undefined reference to `_imp__qpycore_pyqtSignal_Type ' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_init.o):qpycore_init.cp p:(.text+0xf): undefined reference to `_imp__qpycore_pyqtWrapperType_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_init.o):qpycore_init.cp p:(.text+0x1a): undefined reference to `_imp__qpycore_pyqtWrapperType_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_init.o):qpycore_init.cp p:(.text+0x30): undefined reference to `_imp__qpycore_pyqtWrapperType_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_init.o):qpycore_init.cp p:(.text+0xc6): undefined reference to `_imp__qpycore_pyqtWrapperType_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_types.o):qpycore_types. cpp:(.text+0x644): undefined reference to `_imp__qpycore_pyqtProperty_Type' C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303\qpy\QtCore\release/libqpycore.a(qpycore_types.o):qpycore_types. cpp:(.text+0x83d): undefined reference to `_imp__qpycore_pyqtSignal_Type' collect2: ld returned 1 exit status mingw32-make[1]: *** [QtCore.pyd] Error 1 mingw32-make[1]: Leaving directory `C:/Users/cartman/Downloads/PyQt-win-gpl-4.5- snapshot-20090303/PyQt-win-gpl-4.5-snapshot-20090303/QtCore' mingw32-make: *** [all] Error 2 C:\Users\cartman\Downloads\PyQt-win-gpl-4.5-snapshot-20090303\PyQt-win-gpl-4.5-s napshot-20090303> Any help is appreciated. -- İsmail DÖNMEZ ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Moltiple_selection
Hi, On Mon, Jan 12, 2009 at 16:08, lucabe...@libero.it wrote: > Hello > > I have made a groupBox with 3 radioButton, how i can make that more than one > radio button can be selected. Radio buttons are exclusive by default, try using checkboxes. Regards, ismail ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] QDialog window buttons
On Fri, Sep 12, 2008 at 18:26, Scott Frankel <[EMAIL PROTECTED]> wrote: > > When I call setWindowFlags(QtCore.Qt.Window), the dialog is presented with > only the maximize button enabled; the close and minimize buttons are > disabled. > > From the docs, it looks like the flags are combinable. However, none of the > combinations I've tried enable the close and minimize buttons. eg: > >form.setWindowFlags(QtCore.Qt.Window | > QtCore.Qt.WindowMinimizeButtonHint) > > For my current purposes, I'm most interested in the close button, though I > haven't found the hint that provides access to it. You can't remove/disable close button because its handled by the window manager, Qt can't do anything there. Regards, ismail ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] pyqt slow
On Sat, Sep 6, 2008 at 21:03, Aminu D <[EMAIL PROTECTED]> wrote: > Hi, >I am wondering if anyone has been successful running pyqt applications on > windows...I have an application that runs smoothly on ubuntu and it took > considerable effort to port it to windows. But even now it runs very slow, > the Qt connections are slow, MySQLdb could be faster but is ok and it keeps > freezing. So I'm asking is PyQt even stable on windows so I can start > exploring other options. I successfully deployed PyQt4 on Windows, speed wise that is. Regards, ismail ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Access custom Qt widgets from PyQt via SIP?
Hi, On Sun, Aug 10, 2008 at 16:56, Phil Thompson <[EMAIL PROTECTED]> wrote: > On Sun, 10 Aug 2008 09:24:47 -0400, Kevin Walzer <[EMAIL PROTECTED]> > wrote: >> In the latest version of Qt (4.4.1), there is a demo called >> "macmainwindow" that builds a Mac-native window for OS X, wrapping some >> platform-specific widgets: >> >> http://doc.trolltech.com/4.4/demos-macmainwindow.html >> >> Specifically, the Mac search field with rounded corners is wrapped as a >> QObject in C++. >> >> Some of the components in this demo, such as the unified toolbar, are >> exposed as API's in Qt and therefore PyQt, but I'm not sure the search >> field is. How can I access this functionality from PyQt using the Qt >> sample code as a basis? Would I need to do this via SIP or does PyQt >> provide hooks for this kind of thing? > > You would need Python Carbon bindings from somewhere (rolling your own with > SIP if really necessary). Also note that with Qt 4.5, its expected that Carbon will be replaced with Cocoa for better OSX integration and 64bit support. Regards, ismail -- Programmer Excuse #11: I figured I didn't need to test because it was obviously correct. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Strange shadowing of hex() function by PyQt4.QtCore
On Fri, Aug 8, 2008 at 10:02, Mark Summerfield <[EMAIL PROTECTED]> wrote: > On 2008-08-08, Boris Barbour wrote: >> Hi, >> >> Importing PyQt4.QtCore seems to alter or shadow the builtin hex() >> function. I'm afraid I haven't tracked things down further - I just >> learnt the hard way to "import" instead of "from import *". However, >> I'm not sure the clash is intended, so I'm reporting it. >> >> Best regards, >> >> Boris > [snip] > > It is unfortunate that doing * imports on PyQt4 brings in some objects > which don't begin with q or Q. Here's a solution for hex shown as an > IDLE session: > >>>> hex(123) >'0x7b' >>>> from PyQt4.QtCore import * >>>> hex(123) > >Traceback (most recent call last): >File "", line 1, in >hex(123) >TypeError: argument 1 of hex() has an invalid type >>>> __builtins__.hex(123) >'0x7b' >>>> # restore built-in hex >>>> hex = __builtins__.hex >>>> hex(123) >'0x7b' This also bite me many times when I was doing a fast hack using from PyQt4.QtCore import *. Shadowing stdlib functions is evil. Regards, ismail -- Programmer Excuse #11: I figured I didn't need to test because it was obviously correct. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Crash when reading negative size of data from QUdpSocket
Hi,
Using latest sip/PyQt snapshots with Qt4.4, see following:
>>> from PyQt4.QtNetwork import QHostAddress, QUdpSocket
>>> socket = QUdpSocket()
>>> success = socket.bind(QHostAddress("0.0.0.0"), )
>>> success
True
>>> socket.readData(-1)
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Simply returning None when a negative size is given is a better idea.
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] compilation problem PyQt4 on ubuntu 6.10
Hi, On Sun, May 18, 2008 at 1:42 PM, Mark Thompson <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to install PyQt4 on XUbuntu 6.10 (Edgy Eft). PyQt4 is available > in the apt package manager, but for some reason it only installs PyQt4 to > the Python2.4 installation, whereas I need it for Python2.5 (also installed > on the system). So I try a "manual" installation. > > I download, unpack, "python2.5 configure.py", make and make install > sip-4.7.5.tar.gz and PyQt-x11-gpl-4.4.tar.gz from the riverbankcomputing.com > website. No special parameters anywhere -- default should be fine for me. > > Sip compiles and installs fine and in the right Python2.5 location. PyQt > configures fine, but "make" gives compile error: > > make[1]: Entering directory `/home/mark/tmp/PyQt-x11-gpl-4.4/QtCore' > g++ -c -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_CORE_LIB -I. > -I/usr/include/python2.5 -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtCore > -I/usr/include/qt4 -I/usr/X11R6/include -o sipQtCoreQMetaType.o > sipQtCoreQMetaType.cpp > sipQtCoreQMetaType.cpp:290: error: 'QTransform' is not a member of > 'QMetaType' > make[1]: *** [sipQtCoreQMetaType.o] Error 1 > make[1]: Leaving directory `/home/mark/tmp/PyQt-x11-gpl-4.4/QtCore' > make: *** [all] Error 2 You need Qt 4.4 for PyQt 4.4. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Building with Visual Studio 2008
Hi, On Sat, May 17, 2008 at 7:01 PM, Kevin Copps <[EMAIL PROTECTED]> wrote: [...] > In order to get sip > to run from within the Python install, I had to add the following line to > the install target of the Makefile inside the sipgen directory: > > copy /y $(TARGET).manifest C:\Python26\$(TARGET).manifest I can confirm that fix myself. Else sip.exe will abort with a C runtime error. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Newbie - QGraphicsItem & QGraphicsScene problems
Hi, On Tue, May 13, 2008 at 8:25 PM, Aysun Bascetincelik <[EMAIL PROTECTED]> wrote: > Hi, > I am trying to implement a simple paint like program. I am having mainly two > problems: > > 1. I have an item class inherited from QGraphicsItem and I use > QGraphicsScene.addItem() to add it to the scene. However, I can only see the > last added item. Although all previous items (when I use > QGraphicsScene.items()) are present and their visible properties are true, > they are not shown on my scene. This thing only happens when I use addItem() > with the class I implemented. If I use addLine() more than once, I can see > all items created by that addLine() function. Not sure about this one but, > 2.The other problem is when I try to select an item with a left mouse click. > I did not implement the mousePressEvent() inside the item class but I > implemented the one in scene class. I can get the mouse scenePos() easily > and use it to add items. After adding an item, if I use itemAt() function > with a new click on the item and scenePos(), it always returns None. I set > the flags of the item all true. To be able to catch mouse events you need to call QGraphicsView::setInteractive(True) on your graphics view object. Regards. -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Updating the windows installer for Qt 4.4
Hi, On Tue, May 13, 2008 at 2:19 PM, Phil Thompson <[EMAIL PROTECTED]> wrote: > On Tuesday 13 May 2008 11:59:48 Giovanni Bajo wrote: > > On 5/13/2008 10:24 AM, Phil Thompson wrote: > > > On Tuesday 13 May 2008 09:16:59 you wrote: > > >> Hi Phil, > > >> > > >> First we will install Qt/MinGW and then your installer ? And we have to > > >> do this for every machine we want our code to run, correct ? > > > > > > Correct. Of course there is nothing to stop you creating your own single > > > installer containing exactly what you need. > > > > > >> Ps: Just of curiosity: Why is that change ? > > > > > > It's too much trouble for me, particularly as building Qt is getting more > > > complicated. > > > > I understand but I think it's a really wrong commercial move. > > > > The only reason for that package to exist was that it allowed people to > > install a complete PyQt version to experiment with a single click. > > Instead, you're now forcing people to go through two different > > installers, one of which even poses questions which are absolutely > > useless and uncomprehensable for Python programmers which are not C++ > > programmers. > > > > I personally saw a *large* increase of interest in Python Windows > > programmers since the consolidated installer was released. It would be a > > shame to see a regression there. > > > > I really hope you reconsider your choice. > > What I might consider doing is producing an alternative installer for Qt, ie. > a Qt-Lite that only includes the bits that PyQt requires. Well if you'll do that please merge it with main PyQt4 package. This really makes it painless to do internal distribution. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Updating the windows installer for Qt 4.4
Hi Phil et al., Is there a chance of updating the windows installer for Qt 4.4? MSVC Express 2008 is giving me a hard time compiling PyQt4 so I would appreciate an updated installer. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Problems Compiling PyQt4.4
Hi, On Fri, May 9, 2008 at 9:53 PM, Gustavo A. Díaz <[EMAIL PROTECTED]> wrote: > Well.. after adding -lpython2.5 to every single Makefile (:S) compiled > perfectly... > Maybe Kubuntu maintainers broke Qt4.4 someway as you said. FWIW this works fine on MacOSX Leopard. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Problems Compiling PyQt4.4
Hi, On Fri, May 9, 2008 at 10:47 AM, Phil Thompson <[EMAIL PROTECTED]> wrote: > On Friday 09 May 2008 04:03:49 Gustavo A. Díaz wrote: >> Hi, >> >> I cant manage to compile right PyQt4.4 latest snapshot. >> I've compiled latest Sip snapshot, latest Qscintilla snapshot and i have >> brand new Qt.4.4 (Kubuntu Hardy). >> I am attaching where starts to give errors... (and it is very long...) > > Looks like it's not finding the Python library. What does the Makefile look > like? I also see this on Ubuntu Hardy. Makefile's LIBS part is missing -lpython2.5. Adding that fixes the issue. I didn't see this problem with May 05 snapshot though so it might be a new problem. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Q(Core)Application.exec_() is not interruptable
Hi, On Thu, May 1, 2008 at 10:54 PM, Ewald de Wit <[EMAIL PROTECTED]> wrote: > On Thursday 01 May 2008 14:28:31 İsmail Dönmez wrote: > > Following code can't be interrupted with CTRL-C : > > >>> import sys > > >>> from PyQt4.QtCore import QCoreApplication > > >>> QCoreApplication.exec_(sys.argv) > > > > Is this somehow intended and is there a way to overcome this? > > You can catch the signal like this: > > import signal > signal.signal(signal.SIGINT, signal.SIG_DFL) > > > import sys > from PyQt4.QtCore import QCoreApplication > app = QCoreApplication(sys.argv) > app.exec_() That indeed works, thanks for the tip! -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] QDataStream shouldn't accept str as first argument
Hi,
Following code will crash with PyQt4 snapshot and older versions :
>>> a = str("")
>>> b = QDataStream(a, QIODevice.ReadOnly)
>>> b.readDouble()
zsh: segmentation fault python
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Q(Core)Application.exec_() is not interruptable
Hi all, Following code can't be interrupted with CTRL-C : >>> import sys >>> from PyQt4.QtCore import QCoreApplication >>> QCoreApplication.exec_(sys.argv) Is this somehow intended and is there a way to overcome this? Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Problem with QDataStream and QString
Hi again,
Looks like I am back to QDataStream problems and here is the testcase :
>>> from PyQt4.QtCore import *
>>> a = QByteArray()
>>> b = QDataStream(a, QIODevice.ReadWrite)
>>> b << QString("123")
>>> b.device().seek(0)
True
>>> b.readString()
''
I was expecting the last output to be "123" instead of empty string.
Any idea what I am doing wrong here?
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Re: QUdpSocket problem
On Thu, Apr 10, 2008 at 9:24 AM, İsmail Dönmez <[EMAIL PROTECTED]> wrote: > Hi all, > > In Qt following works : > > QUdpSocket sock = new QUdpSocket(); > sock.bind(QHostAdress.Any, ) Read that as, QUdpSocket sock; sock.bind(QHostAdress.Any, ); of course ;) Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] QUdpSocket problem
Hi all,
In Qt following works :
QUdpSocket sock = new QUdpSocket();
sock.bind(QHostAdress.Any, )
But in PyQt it doesn't like it :
>>> sock = QUdpSocket()
>>> sock.bind(QHostAddress.Any, )
Traceback (most recent call last):
File "", line 1, in ?
TypeError: argument 2 of QUdpSocket.bind() has an invalid type
However if I don't use an enum it works :
>>> sock.bind(QHostAddress("0.0.0.0"), )
True
Any ideas?
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Reading from empty QDataStream crashes
Hi all, Using Qt 4.3.4 , PyQt4 snapshot from 20071220 , sip 4.7.4 following example crashes python : >>> from PyQt4.QtCore import * >>> a = QByteArray() >>> b = QDataStream(a, QIODevice.ReadOnly) >>> b.readString() zsh: segmentation fault python If you write same code using C++ you get an empty string instead which is more preferable over a crash. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: PyQt v4.3.3 and SIP v4.7.2 Released
Thursday 06 December 2007 07:04:50 Gerard Vermeulen yazmıştı: > On Wed, 5 Dec 2007 22:01:52 + > > Phil Thompson <[EMAIL PROTECTED]> wrote: > > PyQt v4.3.3 and SIP v4.7.2 have been released and are available from > > the usual places. These are mainly bug fix releases. > > > > The Windows binary installer has been updated with Qt v4.3.3, eric > > v4.0.3 and the latest version of OpenSSL. > > > > (PyQt v4.3.2 never made it out the door as Qt v4.3.3 was released 30 > > minutes after it was tagged.) > > Is SIP v4.7.2 still supposed to work with PyQt v3.17.3? > > I get for instance: > > sipqtpart1.cpp: In function 'PyObject* slot_QRect___ne__(PyObject*, > PyObject*)': sipqtpart1.cpp:22494: error: 'class QRect' has no member > named 'operator!=' Same problem here and there are no PyQt3 snapshots to test it seems. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] pykde segmentation fault - debian etch
Thursday 06 December 2007 00:44:15 Giacomo Lacava yazmıştı:
> >> import kio, kdecore
> >> kio.KIO.NetAccess.download(kdecore.KURL("http://www.google.com";),"/home/
> >>myuser/tempfile")
This kinda usage is wrong, you need to create a KApplication object first.
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE4 Update
[... Forgot to CC the list ...] On Monday 03 September 2007 23:05:03 Jim Bublitz wrote: > On Monday 03 September 2007 12:08, Hans-Peter Jansen wrote: > > Awesome, Jim. > > > > Am Montag, 3. September 2007 18:14 schrieb Jim Bublitz: > > > The module lineup is about the same as PyKDE3, with a few changes. > > > kfile has been rolled into the kio module, kabc/kresource are dropped, > > > kmdi no longer exists, kspell is now in kdecore/kdeui as Sonnet, the > > > solid module has been added, along with (tentatively) two modules that > > > allow scripting plugins for the Kate editor. > > > > Could you elaborate the reasoning behind dropping kabc/kresource briefly? > > > > Is it missing upstream also? > > Yeah - I don't know where they've gone. Are they in kdepim? They're no > longer in kdelibs (or kdebase, or kdesdk). I think akonadi[0] replaces it. [0] http://pim.kde.org/akonadi/ Regards, ismail -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Can't load UI files under Turkish locale
On Friday 10 August 2007 21:46:12 Giovanni Bajo wrote: > On 8/10/2007 1:01 PM, Ismail Dönmez wrote: > >>> Ping? > >> > >> I'm waiting for your reply to Giovanni's question. > > > > To reply Giovanni, yes uic is running from a program who uses system > > locale which is tr_TR.UTF-8. > > Are you saying that, in your system, as soon as you start the Python > interpreter, the locale is tr_TR.UTF-8? Or that your application changes > it? The application switches to system locale on startup. > Anyway, I must say that, in either case, uic should probably be locale > independent. Indeed. [...] > Your suggested fix seemed like the best solution. Don't know where to place it though, its a generic function which might be needed elsewhere. Its interesting python itself doesn't have such functionality. Regards, ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Can't load UI files under Turkish locale
On Friday 10 August 2007 10:42:49 Phil Thompson wrote: > On Friday 10 August 2007 1:21 am, Ismail Dönmez wrote: > > Ping? > > I'm waiting for your reply to Giovanni's question. To reply Giovanni, yes uic is running from a program who uses system locale which is tr_TR.UTF-8. Regards, ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Can't load UI files under Turkish locale
On Friday 10 August 2007 10:42:49 Phil Thompson wrote: > On Friday 10 August 2007 1:21 am, Ismail Dönmez wrote: > > Ping? > > I'm waiting for your reply to Giovanni's question. I can't see his reply in my mailer :-/ I will check web archives, thanks. Regards, ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Can't load UI files under Turkish locale
Ping? On Thursday 02 August 2007 14:08:57 Ismail Dönmez wrote: > Hi all, > > uic/properties.py line 220 says : > > getattr(widget, "set%s%s" % (propname[0].upper(), propname[1:]))( > > The propname[0].upper() part is problematic for Turkish locale, because > uppercase of "i" is not "I" in Turkish locale but its i-with-a-dot-above > (İ) . > > So trying to load a UI file results in an error : > > File "/usr/lib/python2.4/site-packages/PyQt4/uic/properties.py", line > 220, in setProperties > getattr(widget, "set%s%s" % (propname[0].upper(), propname[1:]))( > AttributeError: seticon > > Notice the method name is seticon and not setIcon. Somehow ascii only upper > should be done, something like : > > import ascii > > def ascii_upper(s): > trans_table = string.maketrans(string.ascii_lowercase, > string.ascii_uppercase) > return s.translate(trans_table) > > What do you think? > > Regards, > ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Can't load UI files under Turkish locale
Hi all, uic/properties.py line 220 says : getattr(widget, "set%s%s" % (propname[0].upper(), propname[1:]))( The propname[0].upper() part is problematic for Turkish locale, because uppercase of "i" is not "I" in Turkish locale but its i-with-a-dot-above (İ) . So trying to load a UI file results in an error : File "/usr/lib/python2.4/site-packages/PyQt4/uic/properties.py", line 220, in setProperties getattr(widget, "set%s%s" % (propname[0].upper(), propname[1:]))( AttributeError: seticon Notice the method name is seticon and not setIcon. Somehow ascii only upper should be done, something like : import ascii def ascii_upper(s): trans_table = string.maketrans(string.ascii_lowercase, string.ascii_uppercase) return s.translate(trans_table) What do you think? Regards, ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Re: Qt-4.3.0 hangs
On Sunday 29 July 2007 15:34:51 Jeremy Sanders wrote:
> Okay, here is a test python program which appears to demonstrate a hang on
> Ubuntu Feisty with Qt 4.3.0:
>
> import sys
> from PyQt4.QtCore import *
> from PyQt4.QtGui import *
>
> def fileOpenDialog():
> fd = QFileDialog(window, 'foo')
> fd.exec_()
> # hangs before return from dialog
>
> app = QApplication(sys.argv)
>
> window = QWidget()
>
> quit = QPushButton("File dialog", window)
> QObject.connect(quit, SIGNAL("clicked()"),
> fileOpenDialog)
> window.show()
> app.exec_()
>
> If you click on the button a file dialog opens. When the file dialog is
> closed, the program hangs on the futex sys call.
>
> Can anyone reproduce this problem?
>
> This is with the python-qt4 4.1.0ubuntu6 package, qt4-4.3.0-ubuntu1, python
Can't reproduce here on Pardus Linux 2007.2 :
Qt 4.3.0
PyQt4 20070625
Python 2.4.4
Regards,
ismail
--
Perfect is the enemy of good
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Re: Crash with shortcircuit signals
On Wednesday 11 July 2007 00:00:38 Phil Thompson wrote: [...] > Hmm, works for me (even if I up the loop count to 3000). > > Can anybody else reproduce it? Are you on a 32 or 64 bit system? Can reproduce here on 32bit , sip 20070625, PyQt4 20070625, Qt 4.3.0 [~]> python test.py 0 -1480848532 -1480848468 1 -1480848404 -1480848532 2 -1480848468 -1480848404 3 -1480848532 -1480848468 4 -1480848404 -1480848532 5 -1480848468 -1480848404 6 -1480848532 -1480848468 7 -1480848404 -1480848532 8 -1480848468 -1480848404 9 -1480848532 -1480848468 10 -1480848404 -1480848532 11 -1480848468 -1480848404 12 -1480848532 -1480848468 zsh: segmentation fault python test.py Regards, ismail -- Perfect is the enemy of good ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Fwd: compile errors
On Monday 02 July 2007 01:38:22 Thomas Kocourek wrote: > Let's try the correct mailing list 8-) Try the following patch from Fedora: http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/PyKDE/devel/PyKDE-3.16.0-python25.patch /ismail > > -- Forwarded message -- > From: Thomas Kocourek <[EMAIL PROTECTED]> > Date: Sun, 1 Jul 2007 18:33:53 -0400 > Subject: compile errors > To: [EMAIL PROTECTED] > > I followed the instructions to compile PyKDE. The TROUBLESHOOTING > instructions ask that compile errors get reported. I get the following > compiler errors: > > g++ -c -Wno-deprecated-declarations -O2 -g -pipe -Wall > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC -Wall -W > -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I../extra/kde353 > -I/usr/include/kde -I/usr/include/python2.5 > -I/usr/lib64/qt-3.3/mkspecs/default -I/usr/lib64/qt-3.3/include -o > sipkdecorepart0.o sipkdecorepart0.cpp > sip/kdecore/ktimezones.sip: In function 'int > convertTo_KTimezones_ZoneMap(PyObject*, void**, int*, PyObject*)': > sip/kdecore/ktimezones.sip:247: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '2' to 'int PyDict_Next(PyObject*, > Py_ssize_t*, PyObject**, PyObject**)' > sip/kdecore/kmountpoint.sip: In function 'PyObject* > convertFrom_KMountPoint_List(void*, PyObject*)': > sip/kdecore/kmountpoint.sip:142: warning: taking address of temporary > sipkdecorepart0.cpp: In function 'void release_Display(void*, int)': > sipkdecorepart0.cpp:33440: warning: possible problem detected in > invocation of delete operator: > sipkdecorepart0.cpp:33440: warning: invalid use of undefined type > 'struct _XDisplay' > /usr/lib64/qt-3.3/include/qwindowdefs.h:141: warning: forward > declaration of 'struct _XDisplay' > sipkdecorepart0.cpp:33440: note: neither the destructor nor the > class-specific operator delete will be called, even if they are > declared when the class is defined. > sipkdecorepart0.cpp: At global scope: > sipkdecorepart0.cpp:33446: warning: unused parameter 'sipPy' > sipkdecorepart0.cpp:33446: warning: unused parameter 'sipIsErr' > sipkdecorepart0.cpp: In function 'PyObject* convertFrom_Display(void*, > PyObject*)': > sipkdecorepart0.cpp:33487: warning: unused variable 'sipCpp' > sipkdecorepart0.cpp: At global scope: > sipkdecorepart0.cpp:38302: warning: overflow in implicit constant > conversion sip/kdecore/kurl.sip: In function 'PyObject* > slot_KURL_List___getitem__(PyObject*, PyObject*)': > sip/kdecore/kurl.sip:329: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '3' to 'int > PySlice_GetIndicesEx(PySliceObject*, Py_ssize_t, Py_ssize_t*, > Py_ssize_t*, Py_ssize_t*, Py_ssize_t*)' > sip/kdecore/kurl.sip: In function 'int > slot_KURL_List___delitem__(PyObject*, PyObject*)': > sip/kdecore/kurl.sip:297: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '3' to 'int > PySlice_GetIndicesEx(PySliceObject*, Py_ssize_t, Py_ssize_t*, > Py_ssize_t*, Py_ssize_t*, Py_ssize_t*)' > sip/kdecore/kurl.sip: In function 'int > slot_KURL_List___setitem__(PyObject*, PyObject*)': > sip/kdecore/kurl.sip:255: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '3' to 'int > PySlice_GetIndicesEx(PySliceObject*, Py_ssize_t, Py_ssize_t*, > Py_ssize_t*, Py_ssize_t*, Py_ssize_t*)' > sip/kdecore/kconfigdata.sip: In function 'int > convertTo_KEntryMap(PyObject*, void**, int*, PyObject*)': > sip/kdecore/kconfigdata.sip:153: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '2' to 'int PyDict_Next(PyObject*, > Py_ssize_t*, PyObject**, PyObject**)' > sip/kdecore/kconfigbase.sip: In function 'PyObject* > convertFrom_ulonglong(void*, PyObject*)': > sip/kdecore/kconfigbase.sip:309: warning: unused variable 'LongLong' > sip/kdecore/kcompletion.sip: In function 'int > convertTo_KCompletionBase_KeyBindingMap(PyObject*, void**, int*, > PyObject*)': > sip/kdecore/kcompletion.sip:208: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '2' to 'int PyDict_Next(PyObject*, > Py_ssize_t*, PyObject**, PyObject**)' > sip/kdecore/kwinmodule.sip: In function 'int > convertTo_QValueList_2100(PyObject*, void**, int*, PyObject*)': > sip/kdecore/kwinmodule.sip:142: warning: dereferencing type-punned > pointer will break strict-aliasing rules > sip/kdecore/kwinmodule.sip: In function 'PyObject* > convertFrom_QValueList_2100(void*, PyObject*)': > sip/kdecore/kwinmodule.sip:111: warning: unused variable 'inst' > sip/kdecore/kmacroexpander.sip: In function 'int > convertTo_QMap_0200QChar_0200QStringList(PyObject*, void**, int*, > PyObject*)': > sip/kdecore/kmacroexpander.sip:341: error: cannot convert 'int*' to > 'Py_ssize_t*' for argument '2' to 'int PyDict_Next(PyObject*, > Py_ssize_t*, PyObject**, PyObject**)' > sip/kdecore/kmacroexpander.sip: In function 'int > convertTo_QMap_0200QString_0200QStringList(PyObject*, void**, int*, > PyObject*)': > sip/kdecore/kmacroexpander.sip:258: error: cannot convert 'int*' to > 'Py_ssize_t*' for
Re: [PyQt] ANN: PyQt v4.2, PyQt v3.17.1, SIP v4.6 Released
On Wednesday 11 April 2007 15:54:00 Ismail Dönmez wrote: > Hi, > > On Wednesday 11 April 2007 00:32:12 Phil Thompson wrote: > > The latest versions of PyQt4, PyQt3 and SIP have been released and are > > available from the usual places. > > > > PyQt v4.2 allows you to write Qt Designer widget plugins in Python. It > > also allows you to dynamically define new Qt slots, signals and > > properties. Properties defined in this way also behave as Python > > properties. Also included is support for the Qt event loop for the > > standard Python DBus bindings (ie. not the Qt DBus bindings). See the > > NEWS file for the full details. > > > > PyQt v3.17.1 is a minor bug-fix release. It also has internal changes to > > make it less dependent on any future changes to SIP. > > > > SIP v4.6 has support for wchar_t and universal binaries on MacOS/X. It > > also has lots of internal changes to support the Designer plugin support. > > After updating sip and PyQt, PyKDE apps errors out like this: > > Traceback (most recent call last): > File "/usr/kde/3.5/bin/package-manager", line 981, in ? > main() > File "/usr/kde/3.5/bin/package-manager", line 974, in main > kapp.setMainWidget(myapp) > AttributeError: setMainWidget > ERROR: Communication problem with package-manager, it probably crashed. > > here kapp is a KApplication, and rolling back to PyQt works fine. Is this > incompatibility expected? Finally found the reason for this, if QtAssistant support is disabled for some reason (i.e libqassistantclient.so is missing), PyKDE behaves like this. I guess its not the intended behaviour. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE doesn't compile with latest sip & PyQt
On Monday 25 June 2007 15:22:46 Phil Thompson wrote: > On Monday 25 June 2007 9:33 am, Ismail Dönmez wrote: > > Hi Phil, > > > > On Sunday 24 June 2007 12:43:03 Phil Thompson wrote: > > > I think if you use -j2 instead of -i it will compile (and in a > > > reasonable time). I'll update the patch (or SIP). > > > > Should I add back ulonglong headers back or you will change sip? > > Things should be fixed with tonight's SIP snapshot. The patch will be > updated at the same time. Works perfectly now, great thanks. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE doesn't compile with latest sip & PyQt
Hi Phil, On Sunday 24 June 2007 12:43:03 Phil Thompson wrote: > I think if you use -j2 instead of -i it will compile (and in a reasonable > time). I'll update the patch (or SIP). Should I add back ulonglong headers back or you will change sip? Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE doesn't compile with latest sip & PyQt
On Sunday 24 June 2007 13:43:20 Ismail Dönmez wrote: > On Sunday 24 June 2007 12:43:03 Phil Thompson wrote: [...] > > I think if you use -j2 instead of -i it will compile (and in a reasonable > > time). I'll update the patch (or SIP). > > Actually I was using -j2 and this is a Core2Duo 1.8 with 2 GB RAM. Thanks. Apparently shell was frozen for some reason and I couldn't see output, -j2 without -i works fine and gives the same error. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE doesn't compile with latest sip & PyQt
On Sunday 24 June 2007 12:43:03 Phil Thompson wrote: > On Saturday 23 June 2007 10:27 pm, Ismail Dönmez wrote: > > On Saturday 23 June 2007 18:58:24 Phil Thompson wrote: > > > On Wednesday 20 June 2007 6:15 pm, Ismail Dönmez wrote: > > > > Hi all, > > > > > > > > I got the following installed > > > > > > > > sip-20070619 > > > > PyQt-20070613 > > > > gcc 4.2.0 > > > > > > > > Configuring PyKDE 3.16.0 with configure.py -k /usr/kde/3.5 && make > > > > results in : > > > > > > > > g++ -c -Wno-deprecated-declarations -pipe -fPIC -mtune=i686 -O2 -pipe > > > > -fomit-frame-pointer -Wall -W -D_REENTRANT -DQT_NO_DEBUG > > > > -DQT_THREAD_SUPPORT -I. -I../extra/kde353 -I/usr/kde/3.5/include > > > > -I/usr/include/python2.4 -I/usr/qt/3/mkspecs/default > > > > -I/usr/qt/3/include -I/usr/X11R6/include -o sipkdecorepart0.o > > > > sipkdecorepart0.cpp > > > > In file included from sipkdecorepart0.cpp:24: > > > > sip/kdecore/bytearray.sip:26:31: error: sipdcopQValueList.h: No such > > > > file or directory > > > > sipkdecorepart0.cpp:26:27: error: sipqtQVariant.h: No such file or > > > > directory sip/kdecore/kconfigbase.sip:299:61: error: > > > > sipkdecoreKConfigBase.h: No such file or directory > > > > sip/kdecore/kconfigdata.sip:95:33: error: sipkdecoreKEntryMap.h: No > > > > such file or directory > > > > sip/kdecore/kconfigdata.sip:96:30: error: sipkdecoreKEntry.h: No such > > > > file or directory > > > > sip/kdecore/kconfigdata.sip:97:33: error: sipkdecoreKEntryKey.h: No > > > > such file or directory > > > > sip/kdecore/bytearray.sip:582:28: error: sipdcopDCOPRef.h: No such > > > > file or directory > > > > sip/kdecore/bytearray.sip:583:27: error: sipqtQCString.h: No such > > > > file or directory > > > > sip/kdecore/bytearray.sip:667:26: error: sipqtQString.h: No such file > > > > or directory > > > > sip/kdecore/kmacroexpander.sip:123:24: error: sipqtQChar.h: No such > > > > file or directory > > > > sip/kdecore/kmacroexpander.sip:205:30: error: sipqtQStringList.h: No > > > > such file or directory > > > > sip/kdecore/ktimezones.sip:191:33: error: sipkdecoreKTimezone.h: No > > > > such file or directory > > > > sip/kdecore/ktimezones.sip:143:39: error: > > > > sipkdecoreKTimezoneSource.h: No such file or directory > > > > sip/kdecore/kmountpoint.sip:120:35: error: sipkdecoreKMountPoint.h: > > > > No such file or directory > > > > sip/kdecore/kmountpoint.sip:121:38: error: > > > > sipkdecoreKMountPointPtr.h: No such file or directory > > > > sip/kdecore/klockfile.sip:75:44: error: > > > > ../kdecore/sipkdecoreKLockFile.h: No such file or directory > > > > sip/kdecore/kconfigskeleton.sip:125:32: error: sipkdecorelonglong.h: > > > > No such file or directory > > > > sip/kdecore/kconfigskeleton.sip:126:33: error: sipkdecoreulonglong.h: > > > > No such file or directory > > > > sip/kdecore/kconfigskeleton.sip:1086:53: error: > > > > sipkdecoreKConfigSkeletonItemEnumChoice.h: No such file or directory > > > > sip/kdecore/kconfig.sip:196:37: error: sipkdecoreKSharedConfig.h: No > > > > such file or directory > > > > sip/kdecore/kcompletion.sip:155:33: error: sipkdecoreKShortcut.h: No > > > > such file or directory > > > > > > > > > > > > Any ideas appreciated. > > > > > > I've added a patch to the PyKDE download page. It now builds on my > > > system, but I haven't tried running anything. PyKDE should now also > > > build on 64 bit systems against Python v2.5. > > > > > > The patch basically removes unneeded internal stuff and may well build > > > with earlier versions of SIP - I'd be interested in any feedback. > > > > It started fine but now got this, > > > > sipkdecoreKConfigSkeletonItemUInt64.cpp:50: error: 'ulonglong' has not > > been declared > > sipkdecoreKConfigSkeletonItemUInt64.cpp:50: error: 'ulonglong' has not > > been declared > > sipkdecoreKConfigSkeletonItemUInt64.cpp:65: error: expected ',' or '...' > > before '&' token > > sipkdecoreKConfigSkeletonItemUInt64.cpp:65: error: ISO C++ forbids > > declaration of 'ulonglong' with no type > > sipkdecoreKConfigSkeletonItemUInt64.cpp:86: error: 'ulonglong' has not > > been declared > > sipkdecoreKConfigSkeletonItemUInt64.cpp:86: error: 'ulonglong' has not > > been declared > > [...] > > > > I had to use -i else it wouldn't compile with gcc4, was taking too long. > > I used gcc 4.2.0. Thanks for your help. > > I think if you use -j2 instead of -i it will compile (and in a reasonable > time). I'll update the patch (or SIP). Actually I was using -j2 and this is a Core2Duo 1.8 with 2 GB RAM. Thanks. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyKDE doesn't compile with latest sip & PyQt
On Saturday 23 June 2007 18:58:24 Phil Thompson wrote: > On Wednesday 20 June 2007 6:15 pm, Ismail Dönmez wrote: > > Hi all, > > > > I got the following installed > > > > sip-20070619 > > PyQt-20070613 > > gcc 4.2.0 > > > > Configuring PyKDE 3.16.0 with configure.py -k /usr/kde/3.5 && make > > results in : > > > > g++ -c -Wno-deprecated-declarations -pipe -fPIC -mtune=i686 -O2 -pipe > > -fomit-frame-pointer -Wall -W -D_REENTRANT -DQT_NO_DEBUG > > -DQT_THREAD_SUPPORT -I. -I../extra/kde353 -I/usr/kde/3.5/include > > -I/usr/include/python2.4 -I/usr/qt/3/mkspecs/default -I/usr/qt/3/include > > -I/usr/X11R6/include -o sipkdecorepart0.o sipkdecorepart0.cpp > > In file included from sipkdecorepart0.cpp:24: > > sip/kdecore/bytearray.sip:26:31: error: sipdcopQValueList.h: No such file > > or directory > > sipkdecorepart0.cpp:26:27: error: sipqtQVariant.h: No such file or > > directory sip/kdecore/kconfigbase.sip:299:61: error: > > sipkdecoreKConfigBase.h: No such file or directory > > sip/kdecore/kconfigdata.sip:95:33: error: sipkdecoreKEntryMap.h: No such > > file or directory > > sip/kdecore/kconfigdata.sip:96:30: error: sipkdecoreKEntry.h: No such > > file or directory > > sip/kdecore/kconfigdata.sip:97:33: error: sipkdecoreKEntryKey.h: No such > > file or directory > > sip/kdecore/bytearray.sip:582:28: error: sipdcopDCOPRef.h: No such file > > or directory > > sip/kdecore/bytearray.sip:583:27: error: sipqtQCString.h: No such file or > > directory > > sip/kdecore/bytearray.sip:667:26: error: sipqtQString.h: No such file or > > directory > > sip/kdecore/kmacroexpander.sip:123:24: error: sipqtQChar.h: No such file > > or directory > > sip/kdecore/kmacroexpander.sip:205:30: error: sipqtQStringList.h: No such > > file or directory > > sip/kdecore/ktimezones.sip:191:33: error: sipkdecoreKTimezone.h: No such > > file or directory > > sip/kdecore/ktimezones.sip:143:39: error: sipkdecoreKTimezoneSource.h: No > > such file or directory > > sip/kdecore/kmountpoint.sip:120:35: error: sipkdecoreKMountPoint.h: No > > such file or directory > > sip/kdecore/kmountpoint.sip:121:38: error: sipkdecoreKMountPointPtr.h: No > > such file or directory > > sip/kdecore/klockfile.sip:75:44: error: ../kdecore/sipkdecoreKLockFile.h: > > No such file or directory > > sip/kdecore/kconfigskeleton.sip:125:32: error: sipkdecorelonglong.h: No > > such file or directory > > sip/kdecore/kconfigskeleton.sip:126:33: error: sipkdecoreulonglong.h: No > > such file or directory > > sip/kdecore/kconfigskeleton.sip:1086:53: error: > > sipkdecoreKConfigSkeletonItemEnumChoice.h: No such file or directory > > sip/kdecore/kconfig.sip:196:37: error: sipkdecoreKSharedConfig.h: No such > > file or directory > > sip/kdecore/kcompletion.sip:155:33: error: sipkdecoreKShortcut.h: No such > > file or directory > > > > > > Any ideas appreciated. > > I've added a patch to the PyKDE download page. It now builds on my system, > but I haven't tried running anything. PyKDE should now also build on 64 bit > systems against Python v2.5. > > The patch basically removes unneeded internal stuff and may well build with > earlier versions of SIP - I'd be interested in any feedback. It started fine but now got this, sipkdecoreKConfigSkeletonItemUInt64.cpp:50: error: 'ulonglong' has not been declared sipkdecoreKConfigSkeletonItemUInt64.cpp:50: error: 'ulonglong' has not been declared sipkdecoreKConfigSkeletonItemUInt64.cpp:65: error: expected ',' or '...' before '&' token sipkdecoreKConfigSkeletonItemUInt64.cpp:65: error: ISO C++ forbids declaration of 'ulonglong' with no type sipkdecoreKConfigSkeletonItemUInt64.cpp:86: error: 'ulonglong' has not been declared sipkdecoreKConfigSkeletonItemUInt64.cpp:86: error: 'ulonglong' has not been declared [...] I had to use -i else it wouldn't compile with gcc4, was taking too long. I used gcc 4.2.0. Thanks for your help. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] PyKDE doesn't compile with latest sip & PyQt
Hi all, I got the following installed sip-20070619 PyQt-20070613 gcc 4.2.0 Configuring PyKDE 3.16.0 with configure.py -k /usr/kde/3.5 && make results in : g++ -c -Wno-deprecated-declarations -pipe -fPIC -mtune=i686 -O2 -pipe -fomit-frame-pointer -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I../extra/kde353 -I/usr/kde/3.5/include -I/usr/include/python2.4 -I/usr/qt/3/mkspecs/default -I/usr/qt/3/include -I/usr/X11R6/include -o sipkdecorepart0.o sipkdecorepart0.cpp In file included from sipkdecorepart0.cpp:24: sip/kdecore/bytearray.sip:26:31: error: sipdcopQValueList.h: No such file or directory sipkdecorepart0.cpp:26:27: error: sipqtQVariant.h: No such file or directory sip/kdecore/kconfigbase.sip:299:61: error: sipkdecoreKConfigBase.h: No such file or directory sip/kdecore/kconfigdata.sip:95:33: error: sipkdecoreKEntryMap.h: No such file or directory sip/kdecore/kconfigdata.sip:96:30: error: sipkdecoreKEntry.h: No such file or directory sip/kdecore/kconfigdata.sip:97:33: error: sipkdecoreKEntryKey.h: No such file or directory sip/kdecore/bytearray.sip:582:28: error: sipdcopDCOPRef.h: No such file or directory sip/kdecore/bytearray.sip:583:27: error: sipqtQCString.h: No such file or directory sip/kdecore/bytearray.sip:667:26: error: sipqtQString.h: No such file or directory sip/kdecore/kmacroexpander.sip:123:24: error: sipqtQChar.h: No such file or directory sip/kdecore/kmacroexpander.sip:205:30: error: sipqtQStringList.h: No such file or directory sip/kdecore/ktimezones.sip:191:33: error: sipkdecoreKTimezone.h: No such file or directory sip/kdecore/ktimezones.sip:143:39: error: sipkdecoreKTimezoneSource.h: No such file or directory sip/kdecore/kmountpoint.sip:120:35: error: sipkdecoreKMountPoint.h: No such file or directory sip/kdecore/kmountpoint.sip:121:38: error: sipkdecoreKMountPointPtr.h: No such file or directory sip/kdecore/klockfile.sip:75:44: error: ../kdecore/sipkdecoreKLockFile.h: No such file or directory sip/kdecore/kconfigskeleton.sip:125:32: error: sipkdecorelonglong.h: No such file or directory sip/kdecore/kconfigskeleton.sip:126:33: error: sipkdecoreulonglong.h: No such file or directory sip/kdecore/kconfigskeleton.sip:1086:53: error: sipkdecoreKConfigSkeletonItemEnumChoice.h: No such file or directory sip/kdecore/kconfig.sip:196:37: error: sipkdecoreKSharedConfig.h: No such file or directory sip/kdecore/kcompletion.sip:155:33: error: sipkdecoreKShortcut.h: No such file or directory Any ideas appreciated. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] [Errno 4] Interrupted system call
On Monday 28 May 2007 18:54:47 Jeremy Moskovich wrote: > Hi, > I'm having consistent problems using the python subprocess module in > PyQT applications. > > os.read() & os.wait() calls seem to be interrupted intermittently, in a > manner similar to the following stack trace: > > File "/homes/jeremym/programs/python2.5/lib/python2.5/subprocess.py", > line 593, in __init__ > errread, errwrite) > File "/homes/jeremym/programs/python2.5/lib/python2.5/subprocess.py", > line 1046, in _execute_child > data = os.read(errpipe_read, 1048576) # Exceptions limited to 1 MB > OSError: [Errno 4] Interrupted system call > > The only mention I could find about this online is at: > http://mail.python.org/pipermail/python-list/2007-February/427031.html > which just recommends retrying the operation. > > Does anyone know what the root of this problem is? How can it be solved > effectively You might want to try the following patch http://librarian.launchpad.net/6820347/subprocess-eintr-safety.patch . The bug report is @ http://sourceforge.net/tracker/index.php?func=detail&aid=1068268&group_id=5470&atid=105470 /ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Which Linux distros have PyQt4 preinstalled?
On Thursday 10 May 2007 17:42:21 Mark Summerfield wrote: > On Thu 10-May-07, Ismail Dönmez wrote: > > On Thursday 10 May 2007 16:14:12 Mark Summerfield wrote: > > > Hi, > > > > > > I just found out that Kubuntu 7.04 "Feisty Fawn" includes PyQt4 > > > preinstalled (version 4.1). > > > > > > Does anyone know if it is also preinstalled on plain Ubuntu, or on the > > > forthcoming Fedora 7, or indeed on any other Linux distro? > > > > Pardus Linux have PyQt4 in the repository but its not preinstalled (PyQt3 > > is). > > > > Regards, > > ismail > > Thanks, I've found the package names: > > PyQt4 PyQt4-doc python-docs > > but can't see where IDLE is, unless it is in the python-tk package? Its in the python-tk package. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Which Linux distros have PyQt4 preinstalled?
On Thursday 10 May 2007 16:14:12 Mark Summerfield wrote: > Hi, > > I just found out that Kubuntu 7.04 "Feisty Fawn" includes PyQt4 > preinstalled (version 4.1). > > Does anyone know if it is also preinstalled on plain Ubuntu, or on the > forthcoming Fedora 7, or indeed on any other Linux distro? Pardus Linux have PyQt4 in the repository but its not preinstalled (PyQt3 is). Regards, ismail -- Perfect is the enemy of the good signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: PyQt v4.2, PyQt v3.17.1, SIP v4.6 Released
Hi, On Wednesday 11 April 2007 00:32:12 Phil Thompson wrote: > The latest versions of PyQt4, PyQt3 and SIP have been released and are > available from the usual places. > > PyQt v4.2 allows you to write Qt Designer widget plugins in Python. It also > allows you to dynamically define new Qt slots, signals and properties. > Properties defined in this way also behave as Python properties. Also > included is support for the Qt event loop for the standard Python DBus > bindings (ie. not the Qt DBus bindings). See the NEWS file for the full > details. > > PyQt v3.17.1 is a minor bug-fix release. It also has internal changes to > make it less dependent on any future changes to SIP. > > SIP v4.6 has support for wchar_t and universal binaries on MacOS/X. It also > has lots of internal changes to support the Designer plugin support. After updating sip and PyQt, PyKDE apps errors out like this: Traceback (most recent call last): File "/usr/kde/3.5/bin/package-manager", line 981, in ? main() File "/usr/kde/3.5/bin/package-manager", line 974, in main kapp.setMainWidget(myapp) AttributeError: setMainWidget ERROR: Communication problem with package-manager, it probably crashed. here kapp is a KApplication, and rolling back to PyQt works fine. Is this incompatibility expected? Regards. -- Happiness in intelligent people is the rarest thing I know. (Ernest Hemingway) Ismail Donmez ismail (at) pardus.org.tr GPG Fingerprint: 7ACD 5836 7827 5598 D721 DF0D 1A9D 257A 5B88 F54C Pardus Linux / KDE developer signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyKDE] tr()
18 Oca 2007 Per 10:08 tarihinde, Tony Cappellini şunları yazmıştı: > I'm using pyqt/QT4 for the first time. > > In this menuing example below, there is a call to a function called tr(), > but I don't understand what it does or why it's needed. > Additionally, I must be looking in the wrong part of the help file for QT. > I don't see any documentation for tr() > What is this fnction for, when is it needed? See http://doc.trolltech.com/4.2/qobject.html#tr /ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] PyQt4 and Qt 4.2 snapshot
Hi,
I am getting a weird error with PyQt4 4.0 and Qt 4.2 snapshot:
[~/PyQt-x11-gpl-4.0]> python configure.py -q /usr/bin/qmake-qt4
Determining the layout of your Qt installation...
Checking to see if the QtGui module should be built...
An internal error occured. Please report all the output from the program,
including the following traceback, to [EMAIL PROTECTED]
Traceback (most recent call last):
File "configure.py", line 1127, in ?
main(sys.argv)
File "configure.py", line 1094, in main
pyqt.check_modules()
File "configure.py", line 124, in check_modules
check_module("QtGui", "qwidget.h", "QWidget()")
File "configure.py", line 402, in check_module
if check_class(incfile, ctor, mname):
File "configure.py", line 429, in check_class
return compile_qt_program(cfgtest, mname)
File "configure.py", line 358, in compile_qt_program
exe, build = makefile.build_command(name)
File "/usr/lib/python2.4/site-packages/sipconfig.py", line 1639, in
build_command
build.append(self.required_string("CXX"))
File "/usr/lib/python2.4/site-packages/sipconfig.py", line 786, in
required_string
raise ValueError, "\"%s\" must have a non-empty value" % name
ValueError: "CXX" must have a non-empty value
Anyone saw this, any ideas?
Regards,
ismail
--
アニメは本当にすごいすぎるよ !
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] DCOP From Cron
Salı 20 Haziran 2006 17:19 tarihinde, Richard Heck şunları yazmıştı: > I'm writing a simple application to rotate wallpaper every so often, and > I want to run it as a cron job. The basic structure is pretty simple, > and it works fine if I run it in a shell under KDE. But when I run it as > a cron job, it does not connect to the DCOP server. Is there some way to > tell the script which DCOP server to connect to? Maybe try dcop --user $username . Regards, ismail -- 日本のanimeは揺れる ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Problem compiling PyKDE with latest sip
Hi, Cumartesi 3 Haziran 2006 21:06 tarihinde, Detlev Offenbach şunları yazmıştı: > I tried to compile PyKDE (latest snapshot) with the latest sip and got the > following error during the configure step. > [...] > Generating the C++ source for the kdecore module... > sip: KMD5::update() has overloaded functions with the same Python signature > Error: Unable to create the C++ code. Afaik this is known and PyKDE will have to be updated to work with latest sip, you can search mail archive for more info. /ismail -- An eye for eye will make the whole world blind ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] QString in PyQt4 - Request for Comments
On Tuesday 18 October 2005 20:45, you wrote: > İsmail Dönmez wrote: > > I very much like QString's api like endsWith instead of endswith. Its > > small but in the end all those small things matter :) > > Not to pick a fight or anything, but how is this an advantage? Is it > the case that you don't do much string manipulation in Python? I > recognize that Python's method names are not always as consistent as > Qt's, but once you are used to Python's anything else feels strange to > me. Just curious. :-) I do lots of KDE programming in C++ so when I switch to Python its very comfortable that the api is the same. Because you are used to write endsWith for QString and expect such from a string class. So its just you get used to it. Nothing biggie. Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] QString in PyQt4 - Request for Comments
On Tuesday 18 October 2005 20:24, Phil Thompson wrote:
> I'm wondering whether QString should be dropped in PyQt4 in order to make
> it more Pythonic.
>
> At the moment Python strings and unicode strings are automatically
> converted to QStrings when passed as arguments - so there would be no
> change there. If a QString was returned by a method or an operator then a
> unicode string would be returned instead.
>
> Obviously you would lose all of QString's methods and would have to rely on
> what Python gives you for manipulating strings.
>
> One of the limitations of QString has been that you couldn't do...
>
> q = "Py" + QString("Qt")
>
> ...but with current snapshots you can - so this is an argument for keeping
> QString as it has become easier to use.
>
> BTW, the following is a consequence of the additional support...
>
> s = "Py"
> # s is of type str
> s += QString("Qt")
> # s is now of type QString
>
> Comments, opinions welcome.
I very much like QString's api like endsWith instead of endswith. Its small
but in the end all those small things matter :)
Regards,
ismail
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE & KDE 3.5 again
On Monday 17 October 2005 02:22, Jim Bublitz wrote: > On Sunday 16 October 2005 03:33, İsmail Dönmez wrote: > > Hi Jim, > > > > Looks like your fix mentioned in > > http://www.mail-archive.com/pykde%40mats.imk.fraunhofer.de/msg05769.html > > didn't make it to PyKDE-snapshot20051013. Did you just forget or is there > > any problem with it? > > No problem - I just haven't gotten to all the patches from the mailing list > yet. Should be in the next snapshot in a few days. > > I believe you were using the kde-bindings version also (?) - updates there > depend on when and if Simon Edwards can put them in place (depends on the > KDE release rules somewhat, I'd guess). Those files don't necessarily sync > with the snapshots (which is why they work with newer gcc versions and my > releases haven't until recently). Okies. Btw I don't use kdebindings version but snapshots from riverbankcomputing. Hmm also I am a KDE developer myself and KDE 3.5 is in code freeze now but all changes can be merged to KDE4 trunk which doesn't really work right now :) Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] PyKDE & KDE 3.5 again
Hi Jim, Looks like your fix mentioned in http://www.mail-archive.com/pykde%40mats.imk.fraunhofer.de/msg05769.html didn't make it to PyKDE-snapshot20051013. Did you just forget or is there any problem with it? Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Need help on a weird QThread problem
FWIW I switched to Python threading module and everything is ok now. On Friday 30 September 2005 17:27, İsmail Dönmez wrote: > Hi all, > > I implemented a QThread based function to run some external command in my > application. Its works like this : > > main widget: > > command = QThreadClass() > command.start() > > in QThreadClass: > > def run(self): > # Run some external command > > but when the main application exits I get this: > > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "/usr/lib/python2.4/threading.py", line 636, in __exitfunc > self._Thread__delete() > File "/usr/lib/python2.4/threading.py", line 522, in __delete > del _active[_get_ident()] > KeyError: -1211651904 > Error in sys.exitfunc: > Traceback (most recent call last): > File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs > func(*targs, **kargs) > File "/usr/lib/python2.4/threading.py", line 636, in __exitfunc > self._Thread__delete() > File "/usr/lib/python2.4/threading.py", line 522, in __delete > del _active[_get_ident()] > KeyError: -1211651904 > > Googling for the traceback doesn't provide much info, so wondering if > anyone has an idea whats might be going on ? > > P.S: Please note that main app owns main widget instance and it owns the > QThreadClass() instance. > > Regards, > ismail > > ___ > PyKDE mailing listPyKDE@mats.imk.fraunhofer.de > http://mats.imk.fraunhofer.de/mailman/listinfo/pykde ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] Need help on a weird QThread problem
Hi all, I implemented a QThread based function to run some external command in my application. Its works like this : main widget: command = QThreadClass() command.start() in QThreadClass: def run(self): # Run some external command but when the main application exits I get this: Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib/python2.4/threading.py", line 636, in __exitfunc self._Thread__delete() File "/usr/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: -1211651904 Error in sys.exitfunc: Traceback (most recent call last): File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/lib/python2.4/threading.py", line 636, in __exitfunc self._Thread__delete() File "/usr/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: -1211651904 Googling for the traceback doesn't provide much info, so wondering if anyone has an idea whats might be going on ? P.S: Please note that main app owns main widget instance and it owns the QThreadClass() instance. Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE & KDE 3.5
On Monday 26 September 2005 10:33, Jim Bublitz wrote: > On Sunday 25 September 2005 23:55, İsmail Dönmez wrote: > > Hi, > > > > Whenever I compile PyKDE snapshot against KDE 3.5, I have to apply > > attached patch. I don't know how to fix this in sip file generation > > instead so I hope someone else knows :-) > > > > P.S: Patch fixes the compile error saying "CursorShape is not declared in > > this scope" which comes from fixx11h.h > > Looks like a change in fixx11h.h. I'd try adding the #include in > sip/kdecore/fixx11.sip: > > %ModuleHeaderCode > #include > #include > %End > Thanks > You might need to make the same change in sip/kdecore/ktempdir.sip. > Ok > KDE 3.5 isn't supported yet (and isn't released yet as far as I know). Yes I am using SVN and PyKDE works fine so far with it. > Except for some minor details like this, it should work though - it just > won't support any new (to 3.5) methods or classes from Python. No big deal :-) Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] PyKDE & KDE 3.5
Hi, Whenever I compile PyKDE snapshot against KDE 3.5, I have to apply attached patch. I don't know how to fix this in sip file generation instead so I hope someone else knows :-) P.S: Patch fixes the compile error saying "CursorShape is not declared in this scope" which comes from fixx11h.h Regards, ismail diff -u kdecore-orig/sipAPIkdecore.h kdecore/sipAPIkdecore.h --- kdecore-orig/sipAPIkdecore.h 2005-09-24 22:40:13.0 +0300 +++ kdecore/sipAPIkdecore.h 2005-09-24 22:42:03.0 +0300 @@ -78,6 +78,7 @@ #include #include #include +#include #line 27 "sip/kdecore/fixx11h.sip" #include #line 27 "sip/kdecore/kdeversion.sip" ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] KPDF KPart
Çarşamba 21 Eylül 2005 22:05 tarihinde, Rajeev J Sebastian şunları yazmıştı: > On Wednesday 21 September 2005 6:32 pm, Jim Bublitz wrote: > > On Wednesday 21 September 2005 10:50, David Boddie wrote: > > > > > > It's important to use KParts.MainWindow instead of KMainWindow for your > > application - something that's easy to overlook (at least it is for me). > > On the other hand, I did have to use KApplication instead of QApplication. > I guess this was why my code was segfaulting. I didn't have to change my > KPart loading code after noticing David Boddie's (great!) tip to use > KApplication. You need KApplication for almost all KDE classes ( except some parts of KDEUI classes ). Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: SIP v4.3.1 Released
Cumartesi 10 Eylül 2005 19:48 tarihinde, Phil Thompson şunları yazmıştı:
> SIP v4.3.1 has been released and can be found at the usual place. This is
> just a bug fix release. One fix is to the code generator so you should
> rebuild PyQt, PyKDE etc.
>
Something is broken with this SIP release :
[EMAIL PROTECTED] ~/PyQt/PyQt-x11-gpl-snapshot-20050908 $ python configure.py
This is the GPL version of PyQt snapshot-20050908 (licensed under the GNU
General Public License) for Python 2.4.1 on linux2.
Type 'L' to view the license.
Type 'yes' to accept the terms of the license.
Type 'no' to decline the terms of the license.
Do you accept the terms of the license? yes
SIP 4.3.1 is being used.
An internal error occured. Please report all the output from the program,
including the following traceback, to [EMAIL PROTECTED]
Traceback (most recent call last):
File "configure.py", line 1013, in ?
main(sys.argv)
File "configure.py", line 914, in main
sipconfig.error("This version of PyQt requires SIP v%s or later" %
sipcfg.version_to_string(sip_min_version))
File "/usr/lib/python2.4/site-packages/sipconfig.py", line 169, in
__getattr__
raise AttributeError, "\"%s\" is not a valid configuration value or user
option" % name
AttributeError: "version_to_string" is not a valid configuration value or user
option
Regards,
ismail
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Cuma 09 Eylül 2005 03:43 tarihinde şunları yazmıştınız: > I am pretty sure I saw somewhere in PyQt's wiki a recipe for emiting > signals from a non-QObject. Ok found it : http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/361527 Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Cuma 09 Eylül 2005 03:43 tarihinde şunları yazmıştınız: > I am pretty sure I saw somewhere in PyQt's wiki a recipe for emiting > signals from a non-QObject. A search for "QObject" and "emit" resulted in 0 results at http://www.diotavelli.net/PyQtWiki :/ , though funnily I seem to remember seeing the same thing. Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Cuma 09 Eylül 2005 14:11 tarihinde, Eric Jardim şunları yazmıştı: > 2005/9/8, İsmail Dönmez <[EMAIL PROTECTED]>: > > > You are not "faking" MI, with this. You are actualy doing it. > > > > Yeah but its not working as say it does in C++ > > The difference of C++ MI and Python MI, is that one is statically defined, > and the other is resolved dynamically. For us (humans) only what matters is > *behaviour*. > > > BTW, in Qt4, QThread is also a QObject. > > Yeah I noticed too, which is a good thing. > > You should check python-qt4. But don't wait for threads to work with it. I will rather wait for PyQt to support Qt4 . > > Then I can't use QThread functions like start() which shows this is still > > > not > > 100% inheritance. > > Why not? I don't know how PyQt classes are implemented, but they should be > as "new style classes". If not I suspect that MI would not work correctly. > Anyway, there are several ways to achieve the expected behaviour. > > You can do something like: > class Thread(QObject): > def __init__(...) > self.thread = QThread() > ... > > def __getattr__(self, attr): > return geattr(self.thread, attr) > > Don't give up so soon. Well thanks for info but passing an extra QObject to __init__ is way easier and better than MI for _this_ case :-) Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Cuma 09 Eylül 2005 01:52 tarihinde, Eric Jardim şunları yazmıştı:
> 2005/9/8, İsmail Dönmez <[EMAIL PROTECTED]>:
> > Hi all,
> > I need to emit some signals from a class inheriting from QThread so I
> > need to
> > inherit from QObject too but PyQt has no support for multiple inheritance
> > so
> > I tried following code to fake it :
>
> You are not "faking" MI, with this. You are actualy doing it.
Yeah but its not working as say it does in C++
> BTW, in Qt4, QThread is also a QObject.
Yeah I noticed too, which is a good thing.
>
> but it doesn't work as expected and gives attribute error on line 21 :
> > self.emit(PYSIGNAL('success()'), ('',)) part. So its not really
> > inheriting from QObject. I wonder if anyone knows if we can fake multiple
> > inheritance like this or is it impossible ?
>
> Try putting QObject before QThread:
>
> class Thread(QObject, QThread):
> def __init__(self):
> QObject.__init__(self)
> QThread.__init__(self)
> self.emit(PYSIGNAL('success()'), ('',))
Then I can't use QThread functions like start() which shows this is still not
100% inheritance.
Regards,
ismail
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Cuma 09 Eylül 2005 00:22 tarihinde, Mustafa Sakalsiz şunları yazmıştı: > Hi, > > You don't always need to make subclasses of QObject to emit signals. > > You may use another QObject instance to emit signals. > An example: http://www.opendocs.org/pyqt/index.lxp?lxpwrap=x1807%2ehtm > > or you can use QSignal, Qt Assistant have a sample. Thanks, I will have a look at both. Regards, ismail ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] Is it possible to fake multiple inheritance with PyQt ?
Hi all,
I need to emit some signals from a class inheriting from QThread so I need to
inherit from QObject too but PyQt has no support for multiple inheritance so
I tried following code to fake it :
===
from qt import *
class MyQObject(QObject):
def __init__(self):
QObject.__init__(self)
class MyQThread(QThread):
def __init__(self):
QThread.__init__(self)
class Thread(MyQThread, MyQObject):
def __init__(self):
MyQThread.__init__(self)
MyQObject.__init__(self)
self.emit(PYSIGNAL('success()'), ('',))
def test():
foo = Thread()
if __name__ == "__main__":
test()
===
but it doesn't work as expected and gives attribute error on line 21 :
self.emit(PYSIGNAL('success()'), ('',)) part. So its not really inheriting
from QObject. I wonder if anyone knows if we can fake multiple inheritance
like this or is it impossible ?
Regards,
ismail
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] Anyone tried creating a KCModule ?
Hi again, Looking at list archieves there was some activity about using KCModule with PyKDE[1] but I don't see any outcome of that thread. Like did anyone actually wrote a KCModule using PyKDE, if yes can I see the code please? :-) [1] http://mats.imk.fraunhofer.de/pipermail/pykde/2003-July/005612.html Regards, ismail pgpccyVEdkD6C.pgp Description: PGP signature ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Request for Testing
Perşembe 18 Ağustos 2005 10:11 tarihinde, Phil Thompson şunları yazmıştı:
> Although I planned to release the next versions of SIP, PyQt and
> QScintilla this week, I've just made changes to SIP and PyQt that need
> more testing. The changes are more intrusive than I would like at this
> stage, but they are necessary for proper support for the cyclic garbage
> collector.
>
> I would appreciate it if as many people as possible could test the current
> snapshots. I need to know about successful tests as well as unsuccessful
> ones - just drop me a private email that says "it works for me". I won't
> make the final releases until I'm sure it has had a reasonable amount of
> testing.
Hi,
I downloaded latest PyQt & sip snapshot ato test and my old PyKDE apps started
to crash even simple ones like :
===
[EMAIL PROTECTED]:~/PyWork/test3$ cat hwidget.py
# -*- coding: utf-8 -*-
# Form implementation generated from reading ui file 'hwidget.ui'
#
# Created: Çrş Ağu 10 10:13:52 2005
# by: The PyQt User Interface Compiler (pyuic) 3.13
#
# WARNING! All changes made in this file will be lost!
import sys
from qt import *
from kdecore import KCmdLineArgs, KApplication
from kdeui import *
class HWidget(QWidget):
def __init__(self,parent = None,name = None,fl = 0):
QWidget.__init__(self,parent,name,fl)
if not name:
self.setName("HWidget")
self.displayFrame = QFrame(self,"displayFrame")
self.displayFrame.setGeometry(QRect(40,30,421,301))
self.displayFrame.setFrameShape(QFrame.StyledPanel)
self.displayFrame.setFrameShadow(QFrame.Raised)
self.languageChange()
self.resize(QSize(492,376).expandedTo(self.minimumSizeHint()))
self.clearWState(Qt.WState_Polished)
def languageChange(self):
pass
[EMAIL PROTECTED]:~/PyWork/test3$ cat test3.py
#!/usr/bin/env python
# -*- coding: utf-8 -*-
from qt import *
from hwidget import HWidget
import khtml
from kdecore import KApplication, KCmdLineArgs, KAboutData
class HtmlWidget(HWidget):
def __init__(self, parent=None, name="Html Widget", fl=0):
HWidget.__init__(self,parent,name,fl)
self.khtmlPart = khtml.KHTMLPart(self.displayFrame)
self.khtmlPart.begin()
self.khtmlPart.write("Testing Baby!")
self.khtmlPart.end()
self.khtmlPart.view().resize(420,300)
self.khtmlPart.show()
# Workaround PyKDE bug resulting in a crash at exit
def close(self, alsoDelete = 1):
return HWidget.close(self, 1)
if __name__ == "__main__":
import sys
app = KApplication (sys.argv, "test")
hw = HtmlWidget()
app.setMainWidget(hw)
hw.setCaption("Html Widget")
hw.show()
app.exec_loop()
===
So I downloaded latest PyKDE snapshot again and tried to compile but not it
doesn't even compile :
[EMAIL PROTECTED]:~/PyKDE-snapshot20050628$ make
make[1]: Entering directory `/home/cartman/PyKDE-snapshot20050628/dcop'
g++ -c -Wno-deprecated-declarations -pipe -fPIC -mcpu=i686 -O2 -pipe -Wall -W
-D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I../extra/kde340
-I/usr/kde/3.4/include -I/usr/include/python2.4 -I/usr/qt/3/include
-I/usr/X11R6/include -o sipdcoppart0.o sipdcoppart0.cpp
sip/dcop/dcopclient.sip: In function `PyObject*
convertFrom_QValueList_0200QCString(void*)':
sip/dcop/dcopclient.sip:201: error: invalid conversion from `int' to `
sipWrapper*'
make[1]: *** [sipdcoppart0.o] Error 1
make[1]: Leaving directory `/home/cartman/PyKDE-snapshot20050628/dcop'
make: *** [all] Error 2
System Specs :
[EMAIL PROTECTED]:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/specs
Configured
with: /var/tmp/portage/gcc-3.3.5.20050130-r1/work/gcc-3.3.5/configure
--enable-version-specific-runtime-libs --prefix=/usr
--bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130
--includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info
--with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/include/g++-v3
--host=i686-pc-linux-gnu --disable-altivec --enable-nls
--without-included-gettext --with-system-zlib --disable-checking
--disable-werror --disable-libunwind-exceptions --disable-multilib
--enable-java-awt=gtk --enable-languages=c,c++,java --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.3.5-20050130 (Pardus Linux 3.3.5.20050130-r1,
ssp-3.3.5.20050130-1, pie-8.7.7.1)
[EMAIL PROTECTED]:~$ as -V
GNU assembler version 2.16.1 (i686-pc-linux-gnu) using BFD version 2.16.1
Regards,
ismail
--
Biggest lies ever told :
1. The check is in the mail
2. Don't worry
[PyKDE] Simple KHtml program crashing at exit
Hi all,
I have a very simple Khtml program like this
==
demo.py:
==
#!/usr/bin/env python
# -*- coding: utf-8 -*-
from qt import *
from hwidget import HWidget
import khtml
from kdecore import KApplication, KCmdLineArgs, KAboutData
class HtmlWidget(HWidget):
def __init__(self, parent=None, name="Html Widget", fl=0):
HWidget.__init__(self,parent,name,fl)
self.khtmlPart = khtml.KHTMLPart(self.displayFrame)
self.khtmlPart.begin()
self.khtmlPart.write("Testing Baby!")
self.khtmlPart.end()
self.khtmlPart.view().resize(420,300)
self.khtmlPart.show()
if __name__ == "__main__":
import sys
app = KApplication (sys.argv, "test")
hw = HtmlWidget()
app.setMainWidget(hw)
hw.setCaption("Html Widget")
hw.show()
app.exec_loop()
hwidget.py: ( Auto-generated by pyuic)
from qt import *
class HWidget(QWidget):
def __init__(self,parent = None,name = None,fl = 0):
QWidget.__init__(self,parent,name,fl)
if not name:
self.setName("HWidget")
self.displayFrame = QFrame(self,"displayFrame")
self.displayFrame.setGeometry(QRect(40,30,421,301))
self.displayFrame.setFrameShape(QFrame.StyledPanel)
self.displayFrame.setFrameShadow(QFrame.Raised)
self.languageChange()
self.resize(QSize(492,376).expandedTo(self.minimumSizeHint()))
self.clearWState(Qt.WState_Polished)
def languageChange(self):
pass
But at exit program crashes with a reference to KInstance::config I tried
adding KCmdLineArgs to the app thinking that would be the problem but that
didn't result in any change. So I wonder if anyone has any idea about this
problem ?
Regards,
ismail dönmez
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
