Blob Blame History Raw
dbus-python_: Python bindings for D-Bus

.. _dbus-python:


Online documentation can be found at

There is an incomplete tutorial in `doc/tutorial.txt`__
(if you compile dbus-python with `docutils`_' ``rst2html`` tool installed or
you're reading this document on the D-Bus website, there's also an
`HTML version`__).

__ doc/tutorial.txt
__ doc/tutorial.html

`API documentation`_ is generated if you compile dbus-python with `epydoc`_
version 3 and `docutils`_ installed. An `online copy of the API documentation`_
is also available.

.. _API documentation: api/index.html
.. _epydoc:
.. _docutils:
.. _online copy of the API documentation:

To develop on dbus-python, see `doc/HACKING.txt`__ or the `HTML version`__.

__ doc/HACKING.txt
__ doc/HACKING.html

Problems and alternatives

dbus-python might not be the best D-Bus binding for you to use. 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.

In addition, it uses libdbus (which has known problems with multi-threaded
use) and attempts to be main-loop-agnostic (which means you have to select
a suitable main loop for your application).

Alternative ways to get your Python code onto D-Bus include:

* GDBus, part of the GIO module of `GLib`_, via GObject-Introspection and
  `PyGI`_ (uses the GLib main loop and object model)

* QtDBus, part of `Qt`_, via `PyQt`_ (uses the Qt main loop and object model)

.. _GLib:
.. _PyGI:
.. _Qt:
.. _PyQT: