For GLib 2.26 GDBus D-Bus support was merged, providing an API to replace dbus-glib. 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>
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.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus-python/issues/21.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.