axpy
Table of Contents
Installation
pip install axpy
License
axpy is distributed under the terms of the MIT license.
1 maintainer
Metadata
1 maintainer
Release files for axpy 0.0.5
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 | |
|---|---|---|---|---|
| axpy-0.0.5.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axpy-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.2 kB
Release files / axpy-0.0.5.tar.gz
| Download URL | axpy-0.0.5.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a38e11f6278dfa78f53b82b2698a0b4fe0fa4d6cae53c5a395bc13b77d509878
|
|
BLAKE2b-256 checksum How to use checksums |
f3aa0053efd745b49db4497ca2aefabceeaae6a42947a53b57628d1fc788292c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.23.0
|
Release files / axpy-0.0.5-py3-none-any.whl
| Download URL | axpy-0.0.5-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2eaf4064f980d2210b0000b9368d446997d59578e05871cc5d95dbaabb0f000
|
|
BLAKE2b-256 checksum How to use checksums |
bfefccba065de508ed9ad2ab3f2fcaa59ce2384173fdef92d0f309d8ccb20348
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.23.0
|
Security for axpy 0.0.5
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.
