Ubuntu
python-dbusmock package

python-dbusmock 0.29.1-2 source package in Ubuntu

Changelog

python-dbusmock (0.29.1-2) unstable; urgency=medium

  * Ignore .egg-info/ changes during package cleaning.
    The egg-info is rebuilt during binary package build, with a different
    setuptools than the upstream release. This failed building a source
    package after a binary build. (Closes: #1047543)

 -- Martin Pitt <email address hidden>  Fri, 18 Aug 2023 16:45:11 +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 Pocket Published Component Section
Mantic release universe misc

Builds

Mantic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.29.1-2.dsc 2.2 KiB 776ae2975e310f195ae628d60e3e755955075d019d20fda6b9595ffd0330ddf3
python-dbusmock_0.29.1.orig.tar.gz 90.4 KiB b03590057c236d352c38973f4b71ae2c97b3a1cb1dc6f03278ce4072a3716a74
python-dbusmock_0.29.1-2.debian.tar.xz 7.1 KiB 9fe916acba8403938fbb7628ff1d1e06a863097f6dbcccc69d872a8ac794c248

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.