debus: a non-reference DBus implementation
Summary
This is an attempt to make a nice-to-use asynchronous DBus implementation without any extra dependencies and magic.
Why?
There are two main issues with using "the" dbus implementation with python:
- magical dependencies ("what is
import giand how do I get it to work on my embedded device?") - foreign event loop mandatory for certain operations*, while in the end we only need ot read/write to a socket
* AFAIR you can do synchronous calls wihtout the event loop, but definitely can't subscribe to signals without it
Dependecies
debus uses cython. Thus, you need it (and a working build environment for C) to build debus.
At runtime no extra dependencies (except python itself) is needed.
Known limitations
- Only little-endian messages are supported so far
- Methods have to return a tuple to match dbus idea of multiple "out" parameters
1 maintainer
Metadata
1 maintainer
Release files for debus 0.1.12.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| debus-0.1.12.1.tar.gz | 124.9 kB | Without provenance | Details for debus-0.1.12.1.tar.gz |
Release files / debus-0.1.12.1.tar.gz
| Download URL | debus-0.1.12.1.tar.gz |
|---|---|
| Size | 124.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a0b027569875eb41882437e6912ef6de174225c4487df2c564d463db1fd9a23
|
|
BLAKE2b-256 checksum How to use checksums |
83e7f48429c3a385305eb9b2e5fb92d16c9246add02007ce0be59d386e3a6988
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.3
|
Security for debus 0.1.12.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
