[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    dbus-python and gnome
From:       todd rme <toddrme2178 () gmail ! com>
Date:       2011-04-29 4:56:04
Message-ID: BANLkTin80pDukbGpH851iU4ZVUuv-GYc0g () mail ! gmail ! com
[Download RAW message or body]

I am not sure the best mailing list for this, but it seems of general
importance so I am sending it here.

A little background:

If you use python, you are probably aware that there is currently a
big push underway to switch from pythong 2 to python 3.  Most major
distributions will probably be switching within the next couple of
releases.  KDE's python bindings and pyqt4 have supported python 3 for
a while, I believe.

However, a big piece is missing for desktop users: the dbus python
bindings currently only support python 2.  There was some effort to
port to python 3, but it has stalled, as you can see in the following
bug report:

https://bugs.freedesktop.org/show_bug.cgi?id=26420

The problem is the solution of the dbus-python maintainers.  They
appear to be coming to the conclusion that they should abandon
dbus-python entirely, and switch to the glib python bindings instead.
The problem here is that the glib dbus implementation uses GIO.  In
other words, the recommended dbus python bindings will have a hard
dependency on Gnome.  Since KDE and Qt use dbus heavily, the KDE and
Qt python bindings would also depend on Gnome.

Their suggestion for Qt is to make their own independent dbus bindings
from scratch.  The problem here is that there will no longer be any
DE-independent python bindings for dbus, for instance for command-line
programs.  At least for python, dbus will go from being a
desktop-independent solution to one tied to a particular desktop
environment.  This may not be that big of a deal, but it doesn't seem
like a good solution to me.

I thought it would be worthwhile bringing this to your attention
before any decision is set in stone.  It may be too late now to change
it, but I suspect that developers would have a better chance of making
a change than I would.

-Todd
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]