The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for quda 2.0.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 | |
|---|---|---|---|---|
| quda-2.0.39.tar.gz | 40.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quda-2.0.39-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.1 kB
Release files / quda-2.0.39.tar.gz
| Download URL | quda-2.0.39.tar.gz |
|---|---|
| Size | 40.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33175125e9cb774198889efe0f471fc8c1dd07567c6a48f89a5a14f335a1733b
|
|
BLAKE2b-256 checksum How to use checksums |
8befe275f0e5d6a21fcaad17c40c60a3fa29b499b442b3d2ec15249c397e0ac7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Release files / quda-2.0.39-py3-none-any.whl
| Download URL | quda-2.0.39-py3-none-any.whl |
|---|---|
| Size | 55.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b537ef14e60a487205402b027f2244bedf198492209d749bfe1f7b38409a0949
|
|
BLAKE2b-256 checksum How to use checksums |
f7dd72fcbd68d2d8788198841bb552449071ca9a1c8c86129c2b21aeef04c57a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Security for quda 2.0.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.
