python-dbusmock 0.28.6-1 source package in Ubuntu

Changelog

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

  * New upstream version:
    - Allow sending signals from a specific path (thanks Peter Hutterer)
    - logind: Adjust for systemd 252
    - Use setuptools_scm to determine version
  * debian/copyright: Update to current upstream copyrights
  * debian/watch: Move to PyPI. GitHub's release page became obfuscated and
    cannot be processed by uscan any more.

 -- Martin Pitt <email address hidden>  Wed, 12 Oct 2022 07:31:35 +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

Builds

Kinetic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.28.6-1.dsc 2.2 KiB 7abc480205cf64eae6f057e1a10ef5e487937bcd3dc42c44b5ba0032327dfbbc
python-dbusmock_0.28.6.orig.tar.gz 88.5 KiB 3b496fab84aff3936054f747e9a22bb07ac5783b1d967c6cc39536c7ba315fce
python-dbusmock_0.28.6-1.debian.tar.xz 6.7 KiB d52a7b0ca09e4c4adcde23e0eae0487a76936372c0fd4dc1f310ddb2140755f9

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.