CircuitPython Manager
CircuitPython Manager helps with deploying projects to CircuitPython devices.
Features
- Automatically detects CircuitPython device path.
- Backs up the CircuitPython device before deploying to allow recovery.
- Simple command to restore a backup to the CircuitPython device in case something goes wrong.
Requirements
- Linux. May work elsewhere but not tested.
Installation
You can install CircuitPython Manager via pip from PyPI:
$ pip install circman
Quick Start
Connect your CircuitPython device to your computer using USB and wait for the mount to appear.
Change to the directory of your CircuitPython project. The default is for the project source code to be in src/ relative to the project directory.
Then run the deploy.
$ circman deploy
A backup of the CircuitPython device will be created and then the project source code will be copied to the CircuitPython device.
If you need to restore the code from before the deploy use the restore command.
$ circman restore
To list all available backups:
$ circman list
If you made a change directly on the CircuitPython device you can copy it back to the project source directory. The default destination directory is src/. No backup of the destination is created prior to copying so use with caution. Ideally the destination directory is under version control to identify changes and restore if needed.
$ circman sync
Usage
Please see the Command-line Reference for details.
Contributing
Contributions are very welcome. To learn more, see the Contributor Guide.
License
Distributed under the terms of the MIT license, CircuitPython Manager is free and open source software.
Issues
If you encounter any problems, please file an issue along with a detailed description.
Credits
Device path detection code (find_device()) was copied from Adafruit's circup project.
This project was generated from @cjolowicz's Hypermodern Python Cookiecutter template.
Metadata
Release files for circman 0.3.0
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 |
|---|---|---|---|---|
| circman-0.3.0.tar.gz | 5.8 kB | Without provenance | Details for circman-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| circman-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for circman-0.3.0-py3-none-any.whl |
Total release size: 12.0 kB
Release files / circman-0.3.0.tar.gz
| Download URL | circman-0.3.0.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ef0118f258f537239e35e473d7cb019abfba5dafdbf1cd7bce2651777fd8e2f
|
|
BLAKE2b-256 checksum How to use checksums |
24249f00a59e0fd62fc0bfbf9c2ba7075305f98d1935e5966731ce8d5c9c0214
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.2
|
Release files / circman-0.3.0-py3-none-any.whl
| Download URL | circman-0.3.0-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8bd9ee579d45fabf565b10294f11c16bf88bad76f43bcd1a356517c8ccf01f17
|
|
BLAKE2b-256 checksum How to use checksums |
d4c48a74c1f083258dfde21d7be36f7c74f3410f89452a5572533da5344e9427
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.2
|
Security for circman 0.3.0
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.