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