The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for axiompy 0.2.1
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 | |
|---|---|---|---|---|
| axiompy-0.2.1.tar.gz | 8.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axiompy-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.8 kB
Release files / axiompy-0.2.1.tar.gz
| Download URL | axiompy-0.2.1.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a70607918841a957d1a5a64b58ae4ff5afbf4136f66dfb7cebd1ce5d7fc298be
|
|
BLAKE2b-256 checksum How to use checksums |
93379c762c2033339693671024412dea1ec7f3d0c129f5e9909dfa020499cd63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.2
|
Release files / axiompy-0.2.1-py3-none-any.whl
| Download URL | axiompy-0.2.1-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f06c183985d956e521cd165a8fc65aad19c33e1f84df9774b6bf4fe9918de2d
|
|
BLAKE2b-256 checksum How to use checksums |
b24a1d152d7454b0f6ea816e7607f8558b314ab422a3c64471c1efa50cc1191a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.2
|
Security for axiompy 0.2.1
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.
