| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
set() has been a built-in since 2.4, and we don't support older versions.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Specifically, DBusException and its subclasses no longer have the remote
traceback by default (although subclasses can turn it back on again
by setting include_traceback = True, and the various "programmer error"
subclasses of DBusException do have this set).
Hopefully this will stop people thinking it's a dbus-python or
telepathy-python bug when a D-Bus API like Telepathy deliberately raises an
error (and so dbus-python or telepathy-python is visible in the traceback).
|
| |
|
|
|
|
| |
By either appending to a list of callbacks, or subclassing and providing a
method, you can be notified when connections are added or removed.
Inspired by the DBusServer patch from Huang Peng.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This affects code with copyright statements from the following individuals:
* Anders Carlsson
* Colin Walters
* David Zeuthen
* Rob Taylor
and the following companies:
* Collabora Ltd. (represented by me)
* Red Hat Inc. (represented by Havoc Pennington)
|
| | |
|
| |
|
|
|
|
| |
Havoc's permission
(Message-ID: <815098350709271800k2505485dlef9414609d392b48@mail.gmail.com>)
|
| | |
|
| |
|
|
| |
removing all references to the LGPL as a result
|
| |
|
|
|
| |
This fixes incorrect Python path for docs and tests if doing an out-of-tree
build using an absolute path for $(srcdir), and is also less ugly.
|
| | |
|
| | |
|
| |
|
|
| |
object path (bugs.fd.o #11794)
|
| |
|
|
| |
already used seconds). Add regression tests
|
| |
|
|
| |
BusName ctor
|
| |
|
|
|
|
|
|
| |
In the process, simplify the signal decorator a bit - don't allow the signal
to be emitted from a subset of interfaces (removing connection_keyword),
deprecate path_keyword, disallow path_keyword on objects that support multiple
object paths, and add rel_path_keyword. This is an API removal since previous
patches, but is compatible with the last release.
|
| |
|
|
|
|
| |
Also allow them to be exported on more than one object path or even connection.
dbus.decorators: Allow connection_keyword on signals and methods, so we can
tell which connection to use for any follow-up actions.
|
| | |
|
| | |
|
| |
|
|
| |
This is equivalent to dbus_connection_list_registered() in libdbus.
|
| |
|
|
|
|
|
|
|
|
| |
This prevents a deadlock when a signal match that's tracking name owner
changes is removed, causing a match on NameOwnerChanged to be removed too.
(Debian bug#426412)
Also move more of the tree manipulation inside the lock, to be nice to
anyone attempting a port to implementations without a GIL (mainly IronPython),
and add a regression test for the above bug.
|
| |
|
|
| |
intermittent failures
|
| |
|
|
| |
Also add a simple unit test for it.
|
| |
|
|
|
| |
(Actually tested by connecting to the bus daemon, because I haven't implemented
a Python binding for DBusServer yet.)
|
| |
|
|
| |
GetNameOwner too
|
| | |
|
| |
|
|
|
|
| |
* Let exported methods receive the path, destination and raw message via
kwargs, as well as the sender
* Let exported signals be emitted from a variable object-path
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
More specifically: when a service method with no signature synchronously
returns a tuple that is not a Struct, interpret it as a multi-valued return,
rather than as a structure.
This is a common Python idiom, and returning a struct makes little sense
anyway when D-Bus lets you return multiple values.
Returned lists are still interpreted as arrays - returning an array is
entirely sensible, and indeed likely to be common.
Async service methods are unaffected (there is no ambiguity), and it's still
possible to return a structure by returning a dbus.Struct with appropriate
contents.
https://bugs.freedesktop.org/show_bug.cgi?id=10174
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
As well as being conventional, this seems to be necessary to avoid having
dbus_py_test.so installed, while still having it be a Libtool shared library
(noinst libraries are helpfully made static).
|
| |
|
|
|
|
|
| |
works)
Also run tests with DBUS_FATAL_WARNINGS and ulimit -c unlimited so they dump
core at the slightest provocation.
|
| |
|
|
|
|
|
|
|
|
|
| |
cases.
This avoids us getting kicked off the bus when trying to put the wrong
number of things in a struct - this used to happen, but was masked by the fact
that the tests ran with service activation, so the service was just killed and
reactivated. Forthcoming changes to get_object make this automatic reactivation
not happen (messages will be directed to the unique name by default, so
stateful communication can work).
|
| |
|
|
| |
cross tests) first
|
| | |
|
| |
|
|
| |
attribute are serialized as that object path. Add that attribute to ProxyObject, dbus.Interface and dbus.service.Object.
|
| |
|
|
| |
variants containing byte, not an array of variants containing string
|
| |
|
|
| |
to call awkwardly-named methods like __getattr__
|
| | |
|
| | |
|
| |
|
|
| |
Also make it possible to fail the async call tests in test-client, and add a test case for utf8_strings in async use.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the process:
HACKING.txt: update
include/dbus-python.h: add some typedefs to make it saner
bus.c, conn.c, conn-methods.c: further alter docstrings to keep epydoc happy
exceptions.c: create exceptions in a more longwinded way for Python 2.5 compatibility
message-get-args.c, bus/__init__.py: tweak docstrings
dbus/introspect_parser.py: make docstring valid reStructuredText
run-test.sh: simplify, since configure now does some of the work
test/*.py: use paths from run-test.sh, cope with out-of-tree builds
test-standalone.py: carry out additional sanity checks
|
| |
|
|
| |
segfault on 0.80rc1)
|
| | |
|