The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aiomodbus 0.6.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 | |
|---|---|---|---|---|
| aiomodbus-0.6.0.tar.gz | 11.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiomodbus-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.7 kB
Release files / aiomodbus-0.6.0.tar.gz
| Download URL | aiomodbus-0.6.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd50d20667b738a73430637b6b338aa33499856aeaa2908c6273931fdcef76aa
|
|
BLAKE2b-256 checksum How to use checksums |
df9f3535b13f618983bf51ea56b5df159ad31e3fd73e86c5adc9904dcbb22c71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / aiomodbus-0.6.0-py3-none-any.whl
| Download URL | aiomodbus-0.6.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d01dd38676e8eb04800996e14e1cfb5677a2fe90f4625c6a2d2df8140139f132
|
|
BLAKE2b-256 checksum How to use checksums |
f41b761759e35aa17145b23ccbdddab6c5b338e7e53acd32e33f114af2560a46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for aiomodbus 0.6.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.
