python-dbusmock 0.30.0-1 source package in Ubuntu

Changelog

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

  * New upstream release:
    - api: Add pytest support and helpers
    - api: Factor the server spawning into a new SpawnedMock object (thanks
      Peter Hutterer)
    - doc: generate sphinx docs on
      https://martinpitt.github.io/python-dbusmock/ (thanks Peter Hutterer)
    - cli: Add support for running custom commands on the mock environment
      (thanks Marco Trevisan)

 -- Martin Pitt <email address hidden>  Thu, 30 Nov 2023 07:27:49 +0000

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

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.30.0-1.dsc 2.2 KiB 311a049f49de4263a79df5091e6f722b4437f511200602a37b5b44e4f90be003
python-dbusmock_0.30.0.orig.tar.gz 95.9 KiB dbb59e715b4d88089caed950edf93c46cb5f022ceae5d8ae37064b73baf956c1
python-dbusmock_0.30.0-1.debian.tar.xz 7.2 KiB ee5aaaca17ef4cc40da9f084194bf7bcbdbee9ac519f3d8b82210d4f3844811b

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.