Release files for sicp 0.1.39
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 | |
|---|---|---|---|---|
| sicp-0.1.39.tar.gz | 28.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sicp-0.1.39-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.2 kB
Release files / sicp-0.1.39.tar.gz
| Download URL | sicp-0.1.39.tar.gz |
|---|---|
| Size | 28.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
488c660107693f488068a300b9d45c38550f698c7d2cd44378a6d843e4a8d2e6
|
|
BLAKE2b-256 checksum How to use checksums |
3fb2ea2fd4bc51df2915ff296f6f38a6eb35cc9924e43c77bf8df6963680d9e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.10.0 requests/2.25.0 setuptools/69.0.3 requests-toolbelt/1.0.0 tqdm/4.66.2 CPython/3.9.17
|
Release files / sicp-0.1.39-py3-none-any.whl
| Download URL | sicp-0.1.39-py3-none-any.whl |
|---|---|
| Size | 39.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
230c8d137a9260e10886e95b8a42c88cb5b82f8706ab697e6b71da462b7b9516
|
|
BLAKE2b-256 checksum How to use checksums |
323d8556c5c1f509ef3303d4411e5c1150317b4b974d78202b6490d965c17ddb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.10.0 requests/2.25.0 setuptools/69.0.3 requests-toolbelt/1.0.0 tqdm/4.66.2 CPython/3.9.17
|
Security for sicp 0.1.39
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.
