asyncgpio
AsyncGPIO allows easy access to the GPIO pins on your Raspberry Pi or similar embedded computer.
It is based on libgpiod and its CFFI adapter by Steven P. Goldsmith <sgjava@gmail.com>, as downloaded from github.
To run examples, make sure to install trio first.
Testing AsyncGPIO requires a Linux distribution that enables the mock-GPIO module. As of mid-2020, Debian’s kernel does not include this module, but Raspbian’s does.
If you can compile your own kernel: the option is named CONFIG_GPIO_MOCKUP, in Device Drivers / GPIO support / Memory mapped GPIO drivers / GPIO Testing Driver.
Writing an actual test suite is TODO. There is a more elaborate test script in DistKV-GPIO.
1 maintainer
Metadata
1 maintainer
Release files for asyncgpio 0.5.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 |
|---|---|---|---|---|
| asyncgpio-0.5.1.tar.gz | 27.4 kB | Without provenance | Details for asyncgpio-0.5.1.tar.gz |
Release files / asyncgpio-0.5.1.tar.gz
| Download URL | asyncgpio-0.5.1.tar.gz |
|---|---|
| Size | 27.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ba03bad29f140b5bd117df3863850865b9959db4d17eb6ed710f2237c626965
|
|
BLAKE2b-256 checksum How to use checksums |
b6a6e39148838663f6de3905f46c87c4b55e1638956d0b1cde9aa1ce66be2721
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.8.2 requests/2.25.1 setuptools/59.6.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.10.5
|
Security for asyncgpio 0.5.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.
