Metadata
Release files for pymonics 0.3
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 | |
|---|---|---|---|---|
| pymonics-0.3.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pymonics-0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.1 kB
Release files / pymonics-0.3.tar.gz
| Download URL | pymonics-0.3.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
747234960fa35278fb1ea01b34414de24444a6ee562faab923a52ea23d66d933
|
|
BLAKE2b-256 checksum How to use checksums |
d220b89d6d5107df6e0f585e5266b01aee81e4416b2bd4212dca6dfd671122b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.1
|
Release files / pymonics-0.3-py3-none-any.whl
| Download URL | pymonics-0.3-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9467c58d7d6e75f0da4ae5e11ab0d8ecccd0d85bb4b2a6b2f061e611e5357491
|
|
BLAKE2b-256 checksum How to use checksums |
a181807127f44cbc3682d3b0cb35e05854162c447b0f3162dc9ea2c00acf03b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.1
|
Security for pymonics 0.3
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.