The author of this package has not provided a project description
Metadata
Release files for scipy-pilutil 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 | |
|---|---|---|---|---|
| scipy-pilutil-0.2.1.tar.gz | 8.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scipy_pilutil-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / scipy-pilutil-0.2.1.tar.gz
| Download URL | scipy-pilutil-0.2.1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0455f604f33e8d4aa5316d0c7b56e91754d8ad8ab7b0b3d47ff6dce95c4f7fda
|
|
BLAKE2b-256 checksum How to use checksums |
a777954dc1b11b6dfd008393a55c320630b8a56aef286e1d153c6ec8e78839eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / scipy_pilutil-0.2.1-py3-none-any.whl
| Download URL | scipy_pilutil-0.2.1-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46368b781d6635a2786e426b3e4375e2e5a4ff7e229193b2642431061d92efe0
|
|
BLAKE2b-256 checksum How to use checksums |
878f4f34a62a018bca8080273b9a4fa03a17277d3a7fe4e2276499650efda9ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for scipy-pilutil 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.