diff options
author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2007-08-01 19:58:59 +0100 |
---|---|---|
committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2007-08-01 19:58:59 +0100 |
commit | d3208ff19c3b61ae006403a9096c7a7ac09d4f5f (patch) | |
tree | 6ff22fdc9f93ca3eeb13bdd750e11e316b4751b5 | |
parent | 8a27b1d1164c6c63467d79c497330fefd7c6de6e (diff) |
Mention incompatibility with 0.82.1 more prominently
-rw-r--r-- | NEWS | 18 |
1 files changed, 12 insertions, 6 deletions
@@ -1,6 +1,15 @@ D-Bus Python Bindings 0.82.2 (unreleased) ========================================= +Incompatibility with 0.82.1: + +* If you pass the timeout argument to call_async or an asynchronous proxy + method call and expect it to be in milliseconds, you should change the + argument to be in seconds, and require dbus-python >= 0.82.2. + + This feature didn't work at all in versions prior to 0.82.1, so any code + that works with 0.82.0 or earlier is unaffected. + Features: * @dbus.service.method supports a rel_path_keyword argument for the benefit @@ -13,13 +22,10 @@ Features: Fixes: -* Connection.call_async() measures timeouts in seconds, as was always intended. +* As mentioned under "Incompatibilities" above, Connection.call_async() + measures timeouts in seconds, as was always intended. This means that calls through a proxy object with a reply_handler and - error_handler will measure the timeout in seconds too. call_blocking() - already used seconds, and still does. Existing code using timeouts for - async calls (which would only have worked with 0.82.1) will have to adjust - the timeout length. This applies to the OLPC Sugar environment as used in - Trial 2, for instance. + error_handler will measure the timeout in seconds too. * Introspect() now works on objects exported in more than one location. (fd.o #11794) |