python-dbusmock 0.25.0-1 source package in Ubuntu

Changelog

python-dbusmock (0.25.0-1) unstable; urgency=medium

  * New upstream version 0.25.0:
    - bluez template: Implement adapter discovery, connect, disconnect, and
      removal (thanks Bastien Nocera)
    - Fix changing array properties (thanks Jonas Ã…dahl)
    - Fix CLI upower tests (thanks Marco Trevisan)

 -- Martin Pitt <email address hidden>  Sat, 25 Dec 2021 07:46:28 +0100

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 Pocket Published Component Section

Builds

Jammy: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.25.0-1.dsc 2.2 KiB 6e76b694dacd5d9f9d73b85472dab3bb392dfbe30516f0e1c98aef46a7c8afd1
python-dbusmock_0.25.0.orig.tar.gz 84.6 KiB b0fdd547050656a8139fdc9372a81ad14a84e9654699e6294d96e592f69e10fd
python-dbusmock_0.25.0-1.debian.tar.xz 5.7 KiB 20b37c63891694b4b0a6604569b604a1dc3721c46a226745a6e46532dbcd20c2

Available diffs

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.