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
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-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.