Saleae Logic 2 Automation
logic2-automation implements a Python client for the Logic 2 Automation API.
Documentation can be found at https://saleae.github.io/logic2-automation/
Development
Regenrate protobuf files: uv run build-protobufs
Build wheel: uv build
Publish to PyPi: uv publish
Changelog
1.0.11
- Official release of
1.0rc11. - Add version compatibility tests.
1.0rc11
- Major protobuf version dependency change
- Addressing compatibility between the version of protoc used to generate pb files and the version used at runtime has been an ongoing issue. In v1.0.2 we switched
1.0.8
- Revert change to make grpcio-tools a build-time dependency.
- This dependency was originally moved to build deps so that it would only be installed in that environment. Unfortunately this environment is unaffected by the runtime env, so it was not constrained by the user's existing protobuf/grpc dependencies, causing the protobuf/grpc files to be generated using the latest version. If the user used an earlier version of protobuf that was not compatible with the latest, importing logic-automation would fail. By moving grpcio-tools back to a runtime dependency it can be constrained by the user's existing dependencies.
1.0.7
- Fix builds not building with hatchling 1.19.0.
- Add option for setting gRPC port.
1.0.6
- Moved
grpcio-toolsto build dependencies.
1.0.5
- The .whl build has been fixed, and now includes the generate protobuf/grpc files.
1.0.4
- YANKED!
- The protobuf files (
saleae/grpc) generated during the .whl build were not being included in the .whl file. This was caused by thesaleae/grpcdirectory being added to the .gitignore file. These ignored files have been moved to the parent directory's .gitignore, and an empty .gitignore has been added to the python directory.
- The protobuf files (
- Fix boolean analyzer settings not being sent as the correct type.
1.0.3
- Updated the README to link out to the docs, and move build instructions to BUILD.md.
- Updated the install docs.
1.0.2
- Update the distribution to only include a source distribution so that gRPC/protobuf files can be generated at install time, and be based on the installed version of grpcio/grpcio-tools/protobuf.
1.0.1
- YANKED!
- This release was pulled shortly after it was released due to a conflict between the latest gRPC and the generated protobuf files.
- Change
grpc&grpc-toolsdependency to version>=1.13.0. This lowers the minimum version, and doesn't stick it to a specific version.
1.0.0
- First release
Metadata
Release files for logic2-automation 1.0.11
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 | |
|---|---|---|---|---|
| logic2_automation-1.0.11.tar.gz | 36.2 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| logic2_automation-1.0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 MB
Release files / logic2_automation-1.0.11.tar.gz
| Download URL | logic2_automation-1.0.11.tar.gz |
|---|---|
| Size | 36.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82d1509bee5b74f3fd612972d7a6c2baeb8e2176d026af650663b79de2c97c00
|
|
BLAKE2b-256 checksum How to use checksums |
ee6f006179c1b9bd5b9e20dcd4c276446dd0327dde58921489fb544f097f50ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.10
|
Release files / logic2_automation-1.0.11-py3-none-any.whl
| Download URL | logic2_automation-1.0.11-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1abfa99c7c3949ef84f761dca1a4ed04d08dd05fc5217d76c75bdeb32d7ed2b0
|
|
BLAKE2b-256 checksum How to use checksums |
f6a1eb0876d8fb16642e7e32e84170e7d35ad269b0359c8572249f796e55c5bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.10
|
Security for logic2-automation 1.0.11
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.