This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for upscayl 0.0.0a1
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 | |
|---|---|---|---|---|
| upscayl-0.0.0a1.tar.gz | 5.9 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| upscayl-0.0.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 MB
Release files / upscayl-0.0.0a1.tar.gz
| Download URL | upscayl-0.0.0a1.tar.gz |
|---|---|
| Size | 5.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
426b39c4e9da7f6adcc19300dfc77c65b551f6a4198ede1f8f9ffe71ddbbc239
|
|
BLAKE2b-256 checksum How to use checksums |
73fafd3011181c2d66798ad232a96ab95752a2206cbddbc30b0262a9e70eabbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.4
|
Release files / upscayl-0.0.0a1-py3-none-any.whl
| Download URL | upscayl-0.0.0a1-py3-none-any.whl |
|---|---|
| Size | 6.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e1ead3b9b04cec91d31f179bfc640f4af5f017ecb61fd81ae48717fcceaf6eb
|
|
BLAKE2b-256 checksum How to use checksums |
3db088e7f439b9794def75be09fc0527adfd0a231eb06e5fe9ae122f3e7267e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.4
|
Security for upscayl 0.0.0a1
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.
