python-dbusmock 0.19-1 source package in Ubuntu

Changelog

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

  [ Ondřej Nový ]
  * Use debhelper-compat instead of debian/compat

  [ Martin Pitt ]
  * Move packaging VCS to python-team repository.
    Update Vcs-* tags accordingly. (Closes: #946098)
  * New upstream version 0.19:
    - NetworkManager template: Add "StateReason" property and active connection ID
      (Closes: #947712)
    - Add low-memory-monitor template

 -- Martin Pitt <email address hidden>  Thu, 09 Jan 2020 20:36:10 +0000

Upload details

Uploaded by:
Debian Python Modules Team
Uploaded to:
Sid
Original maintainer:
Debian Python Modules Team
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release universe misc

Builds

Focal: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.19-1.dsc 2.3 KiB b0c88077b064310c614fe46b85517afc4354c8ad9f9b0a9a99c5feb050769188
python-dbusmock_0.19.orig.tar.gz 70.9 KiB 497f30eed2fcd5deaa2633b9622e4e99af4bdfba4e972b350ba630bac6fc86c2
python-dbusmock_0.19-1.debian.tar.xz 4.5 KiB 7213b2a4417400984dec03f684091d008051d0eb04b8d26386a50cb8fe089bbc

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.