Release files for soil 0.20.8
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 | |
|---|---|---|---|---|
| soil-0.20.8.tar.gz | 9.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| soil-0.20.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.3 MB
Release files / soil-0.20.8.tar.gz
| Download URL | soil-0.20.8.tar.gz |
|---|---|
| Size | 9.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d236cc2c8ac16367497781a53a7b25d236a0aba1dc17ec90c6f5939364c10e2
|
|
BLAKE2b-256 checksum How to use checksums |
bf455cbc06ba8e566ef69a50dcdbabe79dc3794e0a56217564fcd39bc8dcfe75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/5.1.0 pkginfo/1.7.1 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.8.10
|
Release files / soil-0.20.8-py3-none-any.whl
| Download URL | soil-0.20.8-py3-none-any.whl |
|---|---|
| Size | 9.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1dfb6d34fea7585e53acd474616b251a0ba1de7edeb249b79a12fd251224101
|
|
BLAKE2b-256 checksum How to use checksums |
646121e5fdacf47ab79f32028fae2ad0635757e953d133f7659fa29eabd974b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/5.1.0 pkginfo/1.7.1 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.8.10
|
Security for soil 0.20.8
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.
