The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for scicomp3 1.1.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 | |
|---|---|---|---|---|
| scicomp3-1.1.0.tar.gz | 89.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scicomp3-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 89.6 MB
Release files / scicomp3-1.1.0.tar.gz
| Download URL | scicomp3-1.1.0.tar.gz |
|---|---|
| Size | 89.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
913c3f7ce2648fd674f5f91e1a9a2aba0d5c0c3d674f4af46607717d128f59b7
|
|
BLAKE2b-256 checksum How to use checksums |
caca978645c110835e0410f1abecdbef5eddf6c2c3b705a876c87cf173d0520e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / scicomp3-1.1.0-py3-none-any.whl
| Download URL | scicomp3-1.1.0-py3-none-any.whl |
|---|---|
| Size | 44.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
157bf27e027625005dc67575e6d71fc3c88b272e6e3b21582bea150733e64469
|
|
BLAKE2b-256 checksum How to use checksums |
d1b4cd404edbbac3021012d2eedb044a6e13d715ba9bf88e631aa3ea0a01a5c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for scicomp3 1.1.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.
