Bug 40661 - uses deprecated dbus-glib (for the main loop glue)
uses deprecated dbus-glib (for the main loop glue)
Status: NEW
Product: dbus
Classification: Unclassified
Component: python
Other All
: medium normal
Assigned To: Simon McVittie
John (J5) Palmieri
Depends on: 31515
  Show dependency treegraph
Reported: 2011-09-06 14:51 UTC by Javier Jardón
Modified: 2011-09-07 02:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Note You need to log in before you can comment on or make changes to this bug.
Description Javier Jardón 2011-09-06 14:51:41 UTC
For GLib 2.26 GDBus D-Bus support was merged, providing an API to replace

See http://library.gnome.org/devel/gio/unstable/gdbus.html and
http://library.gnome.org/devel/gio/unstable/ch28.html .

According to a quick grep this module seems to use dbus-glib:

configure.ac:PKG_CHECK_MODULES(DBUS_GLIB, [dbus-glib-1 >= 0.70])
dbus/mainloop/glib.py:"""GLib main loop integration using libdbus-glib."""
dbus/mainloop/glib.py:    """Initialize threads in dbus-glib, if this has not already been done.
_dbus_glib_bindings/module.c:#include <dbus/dbus-glib.h>
_dbus_glib_bindings/module.c:#include <dbus/dbus-glib-lowlevel.h>
Comment 1 Simon McVittie 2011-09-07 02:50:03 UTC
dbus-python is mostly a binding for libdbus-1: it only uses dbus-glib for its libdbus-1 <-> GLib main-loop integration goo (not a hard runtime dependency - bindings also exist for the Qt main loop), which has no replacement in GDBus, because GDBus doesn't use libdbus-1. So this won't be fixed unless the mainloop stuff gets split out of dbus-glib.

I'm not going to port dbus-python to be a GDBus binding, because I don't think dbus-python is the right API, long-term: using GDBus via gobject-introspection would be a better long-term solution for GNOME projects. (dbus-python also has non-GNOME users.)

I don't know what the long-term answer is for non-GNOME projects (e.g. those that use Qt), but I hope it's something better than dbus-python.