Metadata
Release files for sampling-constraints 0.0.18
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 | |
|---|---|---|---|---|
| sampling-constraints-0.0.18.tar.gz | 12.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sampling_constraints-0.0.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.9 kB
Release files / sampling-constraints-0.0.18.tar.gz
| Download URL | sampling-constraints-0.0.18.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0ea0f5749e4352c77a90f793b38ba8a08347c8ad640c54d2fa4f379243bb3f4
|
|
BLAKE2b-256 checksum How to use checksums |
814ef28d33b4ffb78101fb5ecb55fde7b0ca31f481410edf5c6cd4562e393995
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / sampling_constraints-0.0.18-py3-none-any.whl
| Download URL | sampling_constraints-0.0.18-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b05eb2a7d3bff11407783fc017f180fea9202c019a66601ccfbc49604fa23fb
|
|
BLAKE2b-256 checksum How to use checksums |
6b97dbd3057561a6f82dc26b45ba328aaaaa1a135c874f85537eb2617cc4465c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for sampling-constraints 0.0.18
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.