Python project to set up a connection towards Axis Communications devices and to subscribe to specific events on the metadatastream.
1 maintainer
Metadata
1 maintainer
Release files for axis 56
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 | |
|---|---|---|---|---|
| axis-56.tar.gz | 83.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axis-56-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 171.9 kB
Release files / axis-56.tar.gz
| Download URL | axis-56.tar.gz |
|---|---|
| Size | 83.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f1f21871a7ffc863597aec7c9e525f1d3f1f26e6acbb19e90c94d413677286f
|
|
BLAKE2b-256 checksum How to use checksums |
9fadc9a79ecce291595d5293be20f04c7359a8cc9b7e9e60fecdbc3197614395
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / axis-56-py3-none-any.whl
| Download URL | axis-56-py3-none-any.whl |
|---|---|
| Size | 88.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf459691172fa8e3aaaaa65270402976d71a054dbc68182e77fbe47987263bbb
|
|
BLAKE2b-256 checksum How to use checksums |
4ce98acb1e79fec1edd0fe9f004f41b8343a3d64f5df265a42aaf2c709cc2cfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for axis 56
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.
