The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for SpreadPy 1.0.0
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 | |
|---|---|---|---|---|
| SpreadPy-1.0.0.tar.gz | 16.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| SpreadPy-1.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 29.0 kB
Release files / SpreadPy-1.0.0.tar.gz
| Download URL | SpreadPy-1.0.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
555562e6e237b0883f002ef557db4696c69a856098ffd65d154cd725614280e2
|
|
BLAKE2b-256 checksum How to use checksums |
da6b62ff55de78622738e02a68fdee62adf4c7793afb708f95a0e230354e9ab0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.5
|
Release files / SpreadPy-1.0.0-py2.py3-none-any.whl
| Download URL | SpreadPy-1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f2c527d8af723018a1cf34a99283a96f995ca3eff2a87b5295ae87d38ac578a6
|
|
BLAKE2b-256 checksum How to use checksums |
a91f421116f9e5f4bfc1d1319f35d237e1025fb7093eeb818b40049222942d53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.5
|
Security for SpreadPy 1.0.0
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.
