1 maintainer
Metadata
1 maintainer
Release files for pyscf-shciscf 0.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 | |
|---|---|---|---|---|
| pyscf_shciscf-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyscf_shciscf-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / pyscf_shciscf-0.1.0.tar.gz
| Download URL | pyscf_shciscf-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0ab544853b56d7799d326044d92cd5f66131005b45186dac4d77cbfa7b55517
|
|
BLAKE2b-256 checksum How to use checksums |
d53a1c4e871053193be7a48d837b601348b4b6dec8e27e94de8419870c6ef966
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / pyscf_shciscf-0.1.0-py3-none-any.whl
| Download URL | pyscf_shciscf-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5becd969135c39e54d24092f1151cb0e8f3be7767c1d83a872c8576a40095e9
|
|
BLAKE2b-256 checksum How to use checksums |
55bafcdc8a1ed55b9400979c1eb27f935da853ff29e80d9a24f346d0ed062c77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for pyscf-shciscf 0.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.
