Ubuntu
python-dbusmock package

python-dbusmock 0.31.1-1 source package in Ubuntu

Changelog

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

  * New upstream release:
    - power_profiles_daemon: Move back to original D-Bus name to avoid
      breaking compatibility.
    - Add upower_power_profiles_daemon template for version 0.20 API with new
      D-Bus name.

 -- Martin Pitt <email address hidden>  Fri, 23 Feb 2024 14:08:40 +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
Oracular release universe misc
Noble release universe misc

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.31.1-1.dsc 2.3 KiB 9b3c2d78821d6a0e8ea41f6a04051417d9e2828d25954ca67229dbd88edbe8d5
python-dbusmock_0.31.1.orig.tar.gz 96.4 KiB b23b8e1b51fe2a9b13e617fff6b60b3ed8e536c080cf3498019d223678d5ea49
python-dbusmock_0.31.1-1.debian.tar.xz 7.6 KiB add3f367647e88a6c5c9a9ea5dcd0a00609e7036dab2846baf06cd6e80aec5f3

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.