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 50
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-50.tar.gz | 83.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axis-50-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 171.6 kB
Release files / axis-50.tar.gz
| Download URL | axis-50.tar.gz |
|---|---|
| Size | 83.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c640e0760b3afb167ad8daaf0a1d93508a84240e14561a37e4a728093b89030
|
|
BLAKE2b-256 checksum How to use checksums |
0557e09a661711874bf710f777fac52af8c8ef4fd09cbe29daa81d0743f681b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / axis-50-py3-none-any.whl
| Download URL | axis-50-py3-none-any.whl |
|---|---|
| Size | 88.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23147e61e07f63c096773c0d52125910b9cb095ec24f290aeee846c2c31955cd
|
|
BLAKE2b-256 checksum How to use checksums |
88646ec0f666eb8b872f0a66c327ba663d6cda442e01fb09b5005faba63b008a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for axis 50
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.
