1 D-Bus Python Bindings 0.82.1 (unreleased)
2 =========================================
8 * The tutorial no longer uses interactive-Python syntax, as it confused users.
10 * When making a call via a proxy object with ignore_reply=True, also get the
11 necessary introspection data asynchronously. This can avoid deadlocks in
12 some cases, such as calling methods in the same process (though this is not
13 recommended, for efficiency and sanity reasons).
14 * dbus.lowlevel exposes enough constants to write correct filter functions.
15 * We don't use dbus_watch_get_fd() (deprecated in libdbus) unless our libdbus
16 is too old to have the modern replacement, dbus_watch_get_unix_fd().
20 * Omitting the bus argument in the BusName constructor is deprecated.
21 The fact that it uses the globally shared connection to the session bus by
22 default is uncomfortably subtle.
24 D-Bus Python Bindings 0.82.0 (2007-06-19)
25 =========================================
29 * dbus.service.Object can start off with no Connection or object path, and
30 become exported later. If suitable class attributes are set, objects can
31 even be exported on multiple connections, or with multiple object-paths,
34 * dbus.service.FallbackObject implements a whole subtree of object-path space
37 * ``@method`` accepts a parameter ``connection_keyword`` so methods can find
38 out which connection to use for any follow-up actions.
40 * ``@signal`` has a new parameter ``rel_path_keyword`` which gets the path at
41 which to emit the signal, relative to the path of the FallbackObject.
42 ``path_keyword`` is now deprecated, and will raise an exception if used
43 on an object with ``SUPPORTS_MULTIPLE_OBJECT_PATHS``, including any
48 * In watch_name_owner, only the desired name is watched!
50 * When cleaning up signal matches, errors are ignored. This avoids using up
51 scarce pending-call allowance on dbus-daemon < 1.1, and emitting error
52 messages if we get disconnected.
54 * Signal handlers which are bound to a unique name are automatically
55 disconnected when the unique name goes away, reducing the likelihood that
56 applications will leak signal matches.
58 * Some corrections were made to the tutorial (@service and @method take a
59 parameter dbus_interface, not just interface; fd.o #11209).
61 * ${PYTHON}-config is used to get the Python include path (patch from
62 Sebastien Bacher/Ubuntu, fd.o #11282).
64 D-Bus Python Bindings 0.81.1 (4 June 2007)
65 ==========================================
69 * When an Error message on the bus is represented as a DBusException, the
70 error name is copied into the exception and can be retrieved by
71 get_dbus_name(). Exception handlers should use this instead of looking at
72 the stringified form of the exception, unless backwards compatibility
74 * DBusException objects now get all arguments from the Error message, not
75 just the first (although there will usually only be one). Use the 'args'
76 attribute if you need to retrieve them.
77 * The Connection, BusConnection and Bus classes have a method
78 list_exported_child_objects(path: str) -> list of str, which wraps
79 dbus_connection_list_registered()
80 * You can remove objects from D-Bus before they become unreferenced, by
81 using dbus.service.Object.remove_from_connection()
82 (https://bugs.freedesktop.org/show_bug.cgi?id=10457)
86 * Don't deadlock when removing a signal match that tracks name-owner changes.
87 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426412)
88 * Include child nodes in introspection using list_exported_child_objects()
90 D-Bus Python Bindings 0.81.0 (9 May 2007)
91 =========================================
93 The 'series of tubes' release
94 -----------------------------
96 This is a feature release with support for non-bus-daemon connections
97 and improved GObject integration.
101 * Bus has a superclass dbus.bus.BusConnection (a connection to a bus daemon,
102 but without the shared-connection semantics or any deprecated API)
103 for the benefit of those wanting to subclass bus daemon connections
105 * BusConnection has a superclass dbus.connection.Connection (a
106 connection without a bus daemon) for use in peer-to-peer situations,
107 or distributed pseudo-bus situations without a bus daemon such as
108 Telepathy's Tubes API
110 * dbus.gobject_service.ExportedGObject is like dbus.service.Object, but
111 is also a subclass of GObject (with the necessary metaclass magic to
112 make this work). Until someone has verified that the GObject side of
113 things works as expected too, I consider this API to be potentially
116 * Connection and BusConnection have gained a number of useful methods,
117 including watch_name_owner (track name owner changes asynchronously,
118 avoiding race conditions), call_blocking and call_async (blocking and
119 asynchronous method calls without going via a proxy - note that these
120 are semi-low-level interfaces which don't do introspection), and
121 list_names, list_activatable_names and get_name_owner which are
122 simple wrappers for the corresponding org.freedesktop.DBus methods
124 * dbus.Interface (now also available at dbus.proxies.Interface)
125 and dbus.proxies.ProxyObject now have some reasonably obvious properties.
129 * All keyword arguments called named_service are deprecated in favour of an
130 argument called bus_name (to be compatible with both older and newer
131 dbus-python, you should pass these positional arguments).
133 * The bus keyword argument to dbus.proxies.ProxyObject is deprecated in
134 favour of an argument called conn, because proxies will work on non-bus
135 connections now (again, for maximum compatibility you should use a
136 positional argument for this).
138 * No warning is raised for this, but I consider calling any remote method
139 on a ProxyObject or Interface whose name is either alllowercase or
140 lower_case_with_underscores to be deprecated, and reserve the right
141 to add properties or methods of this form in future releases - use
142 ProxyObject.get_dbus_method if you must call a remote method named in
143 this way. Methods named following TheUsualDBusConvention or
144 theJavaConvention are safe.
148 * Exceptions in signal handlers print a stack trace to stderr (this can
149 be redirected elsewhere with Python's logging framework). Partially
150 addresses fd.o #9980.
152 * The reserved local interface and object path are properly checked for.
154 * When you return a tuple that is not a Struct from a method with no
155 out_signature, it's interpreted as multiple return values, not a
156 single Struct (closes fd.o #10174).
158 * If send_with_reply() returns TRUE but with pending call NULL, dbus-python
159 no longer crashes. This can happen when unexpectedly disconnected.
161 * Arguments are not examined for functions declared METH_NOARGS (this is
162 unnecessary and can cause a crash).
164 Other notable changes:
166 * dbus-python uses the standard Python logging framework throughout.
167 The first time a WARNING or ERROR is generated, it will configure the
168 logging framework to output to stderr, unless you have already
169 configured logging in your application.
171 * The tutorial now advocates the use of add_signal_receiver if all you
172 want to do is listen for signals: this avoids undesired activation,
173 e.g. of Listen or Rhythmbox (!). Addresses fd.o #10743, fd.o #10568.
175 D-Bus Python Bindings 0.80.2 (13 February 2007)
176 ===============================================
177 - Fix numerous memory and reference leaks
178 - Only use -Werror if the user specifically asks for it
179 - Audit tp_dealloc callbacks to make sure they correctly preserve the
181 - Relicense files solely owned by Collabora Ltd. more permissively (LGPL/AFL
182 rather than GPL/AFL) - this includes the tutorial and all the C code
184 D-Bus Python Bindings 0.80.1 (24 January 2007)
185 ==============================================
187 - Install dbus/_version.py, so dbus.__version__ exists again
189 D-Bus Python Bindings 0.80.0 (24 January 2007)
190 ==============================================
191 - The "everything changes" release
192 - Rewrite dbus_bindings (Pyrex) as _dbus_bindings (C) - API changes!
193 - Define what's public API
194 - Move low-level but still public API to dbus.lowlevel
195 - Remove Variant class, add variant_level property on all D-Bus types
196 - Make signal matching keep working as expected when name ownership changes
197 - Use unambiguous D-Bus types when transferring from D-Bus to Python
198 - Follow well-defined rules when transferring from Python to D-Bus
199 - Add utf8_strings and byte_arrays options in various places, so a user
200 can tweak the calling conventions to be more efficient
201 - Raise RuntimeError if user tries to use a connection with no main loop
202 to do something that won't work without one
203 - Make asynchronous method calls actually asynchronous when made before
204 introspection results come back
205 - Redo main loop machinery so we can add pure-Python main loops later without
207 - Allow construction of a dbus.service.Object if you don't have a BusName
209 - Port introspection XML parser from libxml2 (external package) to expat
210 (included with Python)
211 - Port build system from distutils to autoconf/automake/libtool
212 - Install a header file for third-party main loop integration
213 - Make compatible with Python 2.5, including on 64-bit platforms
214 - Add docstrings throughout
215 - Add more tests and examples
216 - Add interoperability tests (which interoperate with Java)
217 - Add copyright notices!
219 D-Bus Python Bindings 0.71 (24 July 2006)
220 ==============================================================
221 - Binary modules are now installed in the correct directory
222 - Distutils exports the dbus and dbus-glib cflags
224 D-Bus Python Bindings 0.70 (17 July 2006)
225 ==============================================================
226 - First release of bindings split
227 - Move to a distutils build enviornment
228 - It is possible to now specify sender_keyword="foo", path_keyword="bar" when
229 adding a signal listener