Ubuntu
python-dbusmock package

python-dbusmock 0.7.2-2~fakesync1 source package in Ubuntu

Changelog

python-dbusmock (0.7.2-2~fakesync1) saucy; urgency=low

  * Fake sync while package is in Debian binary NEW.

python-dbusmock (0.7.2-2) unstable; urgency=low

  * Build a Python 2 package. (LP: #1230141)
 -- Martin Pitt <email address hidden>   Wed, 25 Sep 2013 10:18:40 +0200

Upload details

Uploaded by:
Martin Pitt
Uploaded to:
Saucy
Original maintainer:
Debian Python Modules Team
Architectures:
all
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Saucy: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
python-dbusmock_0.7.2.orig.tar.gz 37.4 KiB b57c621aafff563d60f286d327b9225774ca1f0249edfbd48ab1649b8cda7833
python-dbusmock_0.7.2-2~fakesync1.debian.tar.gz 3.0 KiB ffe4b579cebde32772aa5bf628761eaf48d68966eb9b6f3cfa7ee13790cef4f1
python-dbusmock_0.7.2-2~fakesync1.dsc 2.3 KiB 19647326a462cc6daf7073e3d076129f3015e12251627b2ad97012d5714a97db

Available diffs

View changes file

Binary packages built by this source

python-dbusmock: No summary available for python-dbusmock in ubuntu saucy.

No description available for python-dbusmock in ubuntu saucy.

python3-dbusmock: mock D-Bus objects for tests (Python 3)

 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.