python-dbusmock 0.24.1-1 source package in Ubuntu
Changelog
python-dbusmock (0.24.1-1) unstable; urgency=medium
* New upstream version 0.24.1:
- Do not register standard D-Bus service directories
(Thanks Benjamin Berg)
- templates: Add IIO Sensors Proxy support (Thanks Marco Trevisan)
- Fix importlib module import (Thanks Marco Trevisan)
- Clean up code for most recent pylint version
-- Martin Pitt <email address hidden> Wed, 27 Oct 2021 16:28:46 +0200
Upload details
- Uploaded by:
- Debian Python Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Python Team
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| python-dbusmock_0.24.1-1.dsc | 2.2 KiB | 3aded717387b6322efe87a5c4bd3b0164dc16e9e417cc4c9cdfccef853101d1d |
| python-dbusmock_0.24.1.orig.tar.gz | 83.8 KiB | 56d660bd5f5d0edfe8b0eedfbb9b0814a134eb94b46fca16c379dca68be5724f |
| python-dbusmock_0.24.1-1.debian.tar.xz | 5.6 KiB | 361cb99569a175887edf77c67f608e812b8e8ef7207a0c88fedd072d6028e8bf |
Available diffs
- diff from 0.23.1-2 to 0.24.1-1 (20.4 KiB)
- diff from 0.24.0-1 to 0.24.1-1 (15.5 KiB)
No changes file available.
Binary packages built by this source
- python3-dbusmock: mock D-Bus objects for tests
With python-dbusmock you can easily create mock objects on D-Bus. This is
useful for writing tests for software which talks to D-Bus services such as
upower, systemd, ConsoleKit, gnome-session or others, and it is hard (or
impossible without root privileges) to set the state of the real services to
what you expect in your tests.
.
Mock objects look like the real API (or at least the parts that you actually
need), but they do not actually do anything (or only some action that you
specify yourself). You can configure their state, behaviour and responses as
you like in your test, without making any assumptions about the real system
status.
.
You can use this with any programming language, as you can run the mocker as a
normal program. The actual setup of the mock (adding objects, methods,
properties, etc.) all happen via D-Bus methods on the
org.freedesktop.DBus. Mock interface. You just don't have the convenience
D-Bus launch API that way.
