1 D-Bus Python Bindings 0.82.3 (unreleased)
2 =========================================
4 D-Bus Python Bindings 0.82.2 (2007-08-01)
5 =========================================
7 Incompatibility with 0.82.1:
9 * If you pass the timeout argument to call_async or an asynchronous proxy
10 method call and expect it to be in milliseconds, you should change the
11 argument to be in seconds, and require dbus-python >= 0.82.2.
13 This feature didn't work at all in versions prior to 0.82.1, so any code
14 that works with 0.82.0 or earlier is unaffected.
18 * @dbus.service.method supports a rel_path_keyword argument for the benefit
19 of fallback objects, which provides the method implementation with the path
20 of the object within the exported subtree. For instance, if you have a
21 fallback object exported at /Fallback, and you call a method that has
22 rel_path_keyword='rel_path' on /Fallback and on /Fallback/Some/Where, the
23 method implementation will be called with rel_path='/' and with
24 rel_path='/Some/Where' respectively. (fd.o #11623)
26 * If you have epydoc version 3 (currently in beta), API documention is now
31 * As mentioned under "Incompatibilities" above, Connection.call_async()
32 measures timeouts in seconds, as was always intended.
33 This means that calls through a proxy object with a reply_handler and
34 error_handler will measure the timeout in seconds too.
36 * Introspect() now works on objects exported in more than one location.
39 * Building against Python 2.4 on non-Debian-derived distributions, or a
40 non-default Python version on Gentoo, should work again (revenge
41 of fd.o #11282, thanks Eyal Ben David).
43 D-Bus Python Bindings 0.82.1 (2007-07-11)
44 =========================================
46 The "double precision" release.
50 * Parse the timeout correctly in send_message_with_reply() and
51 send_message_with_reply_and_block(), fixing the use of non-default timeouts
53 * The tutorial no longer uses interactive-Python syntax, as it confused users.
55 * When making a call via a proxy object with ignore_reply=True, also get the
56 necessary introspection data asynchronously. This can avoid deadlocks in
57 some cases, such as calling methods in the same process (though this is not
58 recommended, for efficiency and sanity reasons).
59 * dbus.lowlevel exposes enough constants to write correct filter functions.
60 * We don't use dbus_watch_get_fd() (deprecated in libdbus) unless our libdbus
61 is too old to have the modern replacement, dbus_watch_get_unix_fd().
65 * Omitting the bus argument in the BusName constructor is deprecated.
66 The fact that it uses the globally shared connection to the session bus by
67 default is uncomfortably subtle.
69 D-Bus Python Bindings 0.82.0 (2007-06-19)
70 =========================================
74 * dbus.service.Object can start off with no Connection or object path, and
75 become exported later. If suitable class attributes are set, objects can
76 even be exported on multiple connections, or with multiple object-paths,
79 * dbus.service.FallbackObject implements a whole subtree of object-path space
82 * ``@method`` accepts a parameter ``connection_keyword`` so methods can find
83 out which connection to use for any follow-up actions.
85 * ``@signal`` has a new parameter ``rel_path_keyword`` which gets the path at
86 which to emit the signal, relative to the path of the FallbackObject.
87 ``path_keyword`` is now deprecated, and will raise an exception if used
88 on an object with ``SUPPORTS_MULTIPLE_OBJECT_PATHS``, including any
93 * In watch_name_owner, only the desired name is watched!
95 * When cleaning up signal matches, errors are ignored. This avoids using up
96 scarce pending-call allowance on dbus-daemon < 1.1, and emitting error
97 messages if we get disconnected.
99 * Signal handlers which are bound to a unique name are automatically
100 disconnected when the unique name goes away, reducing the likelihood that
101 applications will leak signal matches.
103 * Some corrections were made to the tutorial (@service and @method take a
104 parameter dbus_interface, not just interface; fd.o #11209).
106 * ${PYTHON}-config is used to get the Python include path (patch from
107 Sebastien Bacher/Ubuntu, fd.o #11282).
109 D-Bus Python Bindings 0.81.1 (4 June 2007)
110 ==========================================
114 * When an Error message on the bus is represented as a DBusException, the
115 error name is copied into the exception and can be retrieved by
116 get_dbus_name(). Exception handlers should use this instead of looking at
117 the stringified form of the exception, unless backwards compatibility
119 * DBusException objects now get all arguments from the Error message, not
120 just the first (although there will usually only be one). Use the 'args'
121 attribute if you need to retrieve them.
122 * The Connection, BusConnection and Bus classes have a method
123 list_exported_child_objects(path: str) -> list of str, which wraps
124 dbus_connection_list_registered()
125 * You can remove objects from D-Bus before they become unreferenced, by
126 using dbus.service.Object.remove_from_connection()
127 (https://bugs.freedesktop.org/show_bug.cgi?id=10457)
131 * Don't deadlock when removing a signal match that tracks name-owner changes.
132 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426412)
133 * Include child nodes in introspection using list_exported_child_objects()
135 D-Bus Python Bindings 0.81.0 (9 May 2007)
136 =========================================
138 The 'series of tubes' release
139 -----------------------------
141 This is a feature release with support for non-bus-daemon connections
142 and improved GObject integration.
146 * Bus has a superclass dbus.bus.BusConnection (a connection to a bus daemon,
147 but without the shared-connection semantics or any deprecated API)
148 for the benefit of those wanting to subclass bus daemon connections
150 * BusConnection has a superclass dbus.connection.Connection (a
151 connection without a bus daemon) for use in peer-to-peer situations,
152 or distributed pseudo-bus situations without a bus daemon such as
153 Telepathy's Tubes API
155 * dbus.gobject_service.ExportedGObject is like dbus.service.Object, but
156 is also a subclass of GObject (with the necessary metaclass magic to
157 make this work). Until someone has verified that the GObject side of
158 things works as expected too, I consider this API to be potentially
161 * Connection and BusConnection have gained a number of useful methods,
162 including watch_name_owner (track name owner changes asynchronously,
163 avoiding race conditions), call_blocking and call_async (blocking and
164 asynchronous method calls without going via a proxy - note that these
165 are semi-low-level interfaces which don't do introspection), and
166 list_names, list_activatable_names and get_name_owner which are
167 simple wrappers for the corresponding org.freedesktop.DBus methods
169 * dbus.Interface (now also available at dbus.proxies.Interface)
170 and dbus.proxies.ProxyObject now have some reasonably obvious properties.
174 * All keyword arguments called named_service are deprecated in favour of an
175 argument called bus_name (to be compatible with both older and newer
176 dbus-python, you should pass these positional arguments).
178 * The bus keyword argument to dbus.proxies.ProxyObject is deprecated in
179 favour of an argument called conn, because proxies will work on non-bus
180 connections now (again, for maximum compatibility you should use a
181 positional argument for this).
183 * No warning is raised for this, but I consider calling any remote method
184 on a ProxyObject or Interface whose name is either alllowercase or
185 lower_case_with_underscores to be deprecated, and reserve the right
186 to add properties or methods of this form in future releases - use
187 ProxyObject.get_dbus_method if you must call a remote method named in
188 this way. Methods named following TheUsualDBusConvention or
189 theJavaConvention are safe.
193 * Exceptions in signal handlers print a stack trace to stderr (this can
194 be redirected elsewhere with Python's logging framework). Partially
195 addresses fd.o #9980.
197 * The reserved local interface and object path are properly checked for.
199 * When you return a tuple that is not a Struct from a method with no
200 out_signature, it's interpreted as multiple return values, not a
201 single Struct (closes fd.o #10174).
203 * If send_with_reply() returns TRUE but with pending call NULL, dbus-python
204 no longer crashes. This can happen when unexpectedly disconnected.
206 * Arguments are not examined for functions declared METH_NOARGS (this is
207 unnecessary and can cause a crash).
209 Other notable changes:
211 * dbus-python uses the standard Python logging framework throughout.
212 The first time a WARNING or ERROR is generated, it will configure the
213 logging framework to output to stderr, unless you have already
214 configured logging in your application.
216 * The tutorial now advocates the use of add_signal_receiver if all you
217 want to do is listen for signals: this avoids undesired activation,
218 e.g. of Listen or Rhythmbox (!). Addresses fd.o #10743, fd.o #10568.
220 D-Bus Python Bindings 0.80.2 (13 February 2007)
221 ===============================================
222 - Fix numerous memory and reference leaks
223 - Only use -Werror if the user specifically asks for it
224 - Audit tp_dealloc callbacks to make sure they correctly preserve the
226 - Relicense files solely owned by Collabora Ltd. more permissively (LGPL/AFL
227 rather than GPL/AFL) - this includes the tutorial and all the C code
229 D-Bus Python Bindings 0.80.1 (24 January 2007)
230 ==============================================
232 - Install dbus/_version.py, so dbus.__version__ exists again
234 D-Bus Python Bindings 0.80.0 (24 January 2007)
235 ==============================================
236 - The "everything changes" release
237 - Rewrite dbus_bindings (Pyrex) as _dbus_bindings (C) - API changes!
238 - Define what's public API
239 - Move low-level but still public API to dbus.lowlevel
240 - Remove Variant class, add variant_level property on all D-Bus types
241 - Make signal matching keep working as expected when name ownership changes
242 - Use unambiguous D-Bus types when transferring from D-Bus to Python
243 - Follow well-defined rules when transferring from Python to D-Bus
244 - Add utf8_strings and byte_arrays options in various places, so a user
245 can tweak the calling conventions to be more efficient
246 - Raise RuntimeError if user tries to use a connection with no main loop
247 to do something that won't work without one
248 - Make asynchronous method calls actually asynchronous when made before
249 introspection results come back
250 - Redo main loop machinery so we can add pure-Python main loops later without
252 - Allow construction of a dbus.service.Object if you don't have a BusName
254 - Port introspection XML parser from libxml2 (external package) to expat
255 (included with Python)
256 - Port build system from distutils to autoconf/automake/libtool
257 - Install a header file for third-party main loop integration
258 - Make compatible with Python 2.5, including on 64-bit platforms
259 - Add docstrings throughout
260 - Add more tests and examples
261 - Add interoperability tests (which interoperate with Java)
262 - Add copyright notices!
264 D-Bus Python Bindings 0.71 (24 July 2006)
265 ==============================================================
266 - Binary modules are now installed in the correct directory
267 - Distutils exports the dbus and dbus-glib cflags
269 D-Bus Python Bindings 0.70 (17 July 2006)
270 ==============================================================
271 - First release of bindings split
272 - Move to a distutils build enviornment
273 - It is possible to now specify sender_keyword="foo", path_keyword="bar" when
274 adding a signal listener