[PyKDE] QtDBus Support in PyQt
mbouchar at bioinfo.ulaval.ca
Sat Oct 28 03:38:14 BST 2006
On Friday 27 October 2006 15:53, Jim Bublitz wrote:
> On Friday 27 October 2006 10:51, Phil Thompson wrote:
> > After working on this for a little while I've decided that I will not
> > support QtDBus in PyQt. Reasons are...
> > - A standard set DBus Python bindings already exist. These are still in
> > active development but the current maintainer seems to be doing a good
> > job, both in terms of backwards compatibility and ensuring they are
> > Pythonic.
Last commit is from 3 months ago. Current python bindings only supports glib
main loop. So, if you want to create an application that acts as a d-bus
server, you must use glib for now. The author has mentionned that he will add
support for generic loops, but has never mentionned Qt. Since using glib main
loop for d-bus support and another for Qt support is impossible, there is a
Currently, you can only create applications that sends d-bus signals using
python and Qt.
> > - QtDBus is more difficult to wrap than the rest of Qt because of it's
> > use of templates and its own type system. Not impossible to wrap - but
> > there would be a list of "things to be aware of" and "differences between
> > Qt and PyQt".
There are already "things to be aware of" when using signals / slots using
> > - The extra work required would delay the release of PyQt v4.1.
> > - As QtDBus is new to most people there isn't a large body of C++
> > experience and code that could be ported to Python.
I have not tried the C++ part of the QtDBus api because I was waiting for the
PyQt version (For now, my only Qt/KDE applications are PyQt/PyKDE ones).
> > I'm happy to reconsider this in the unlikely event that the standard
> > Python bindings prove inadequate.
> At the moment, it isn't clear to me exactly how DBUS and QtDBus will be
> integrated into KDE4. The KDE4 source/binaries I have really only reference
> QtDBus in klauncher, and that doesn't appear to work at the moment
> (although the source and binaries I have are over a month old, so that's
> probably changed).
> As I have absolutely no familiarity with DBUS, I'll have to wait and see
> how it's implemented in KDE4 and then figure out what support I'll provide.
> It may be supporting only parts of DBUS or providing something similar to
> the DCOP extensions in the current PyKDE.
DBUS completely replaces dcop in KDE4. I'm currently testing an up to date
version of KDE/trunk that uses DBUS as interprocess communication. I haven't
looked at the code, but I assume that everywhere there was a DCOP reference
there is now a QtDBus reference.
> PyKDE mailing list PyKDE at mats.imk.fraunhofer.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20061028/61a618bc/attachment.bin
More information about the PyQt