This release is a pre-release and may not be stable for production use.
PiGlow
Library for the Pimoroni Pibrella board, based on the sn3218 IC https://github.com/Gadgetoid/python-sn3218
I have attempted to make this library code compatible with Jason (@Boeeerb) Barnett’s PiGlow examples, he maintains by far the most complete codebase and documentation for the PiGlow here: https://github.com/Boeeerb/PiGlow
Change Log
1.1dev
Made code-compatible with Jason Barnett’s PiGlow library
renamed my ‘led’ method to ‘single’
wrapped inherited ‘set’ to automatically call ‘update’
1.0dev
Initial experimental module
1 maintainer
Metadata
1 maintainer
Release files for pimglow 1.1dev
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 |
|---|---|---|---|---|
| pimglow-1.1dev.tar.gz | 3.1 kB | Without provenance | Details for pimglow-1.1dev.tar.gz |
Release files / pimglow-1.1dev.tar.gz
| Download URL | pimglow-1.1dev.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
adad1d5afdbcbe09b8dd4dc3954a73716c5588ad84849881724cad9f7d2d0b26
|
|
BLAKE2b-256 checksum How to use checksums |
cd581df189d8eb2b9d8be126587e17be68a118aa84d33eb7c30b1db04c2611db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pimglow 1.1dev
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.
