(In reply to comment #42)
> I'd recommend using GDBus for D-Bus in Python 3 code. dbus-python does not
> follow the principle of "In the face of ambiguity, refuse the temptation to
> guess", and can't be changed to not do so without seriously breaking
> compatibility.
>
> Moving from Python 2 to Python 3 seems as good a time as any to switch...
>
> Redesigning dbus-python to make the type system explicit would basically end up
> with something resembling GDBus (but implemented on top of a less tractable
> library with worse thread-safety), and nobody's actively working on it anyway.
(In reply to comment #42)
> I'd recommend using GDBus for D-Bus in Python 3 code. dbus-python does not
> follow the principle of "In the face of ambiguity, refuse the temptation to
> guess", and can't be changed to not do so without seriously breaking
> compatibility.
>
> Moving from Python 2 to Python 3 seems as good a time as any to switch...
>
> Redesigning dbus-python to make the type system explicit would basically end up
> with something resembling GDBus (but implemented on top of a less tractable
> library with worse thread-safety), and nobody's actively working on it anyway.
I see... But it would make dbus dependent on glib. For example, PyQt doesn't expose Qt's support for dbus, for it being too much "C== oriented", according to this: http:// www.riverbankco mputing. co.uk/static/ Docs/PyQt4/ html/introducti on.html# pyqt-components. Is it possible to use GDbus without GLib main loop?