QCPortal
A client interface to the QC Archive Project.
This standalone client serves to hook into QCFractal instances from remote or local locations and is designed for end-users who which to access the QCFractal stores.
Issues
All issues should be reported to the QCFractal issue tracker. This repository is automatically updated from the main QCFractal source code and is only used for deployment of the QCPortal package.
QCPortal Version descriptions with QCFractal
QCPortal's release versions mostly match QCFractal's releases with the following standard form
X.Y.Z
for Major (X), Minor(Y), and Patch(Z) version respectively. However, because Portal is intrinsicly linked to Fractal, the following rules must be adhered to:
- Major release version must be the same as Fractal
- Minor release version must be the same as Fractal
- Patch version is unrestricted and can differ from Fractal
Copyright
Copyright (c) 2018, Molecular Software Sciences Institute (MolSSI)
Acknowledgements
Project based on the Computational Chemistry Python Cookiecutter
Metadata
Release files for qcportal 0.12.3
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 | |
|---|---|---|---|---|
| qcportal-0.12.3.tar.gz | 105.4 kB | Without provenance | Details |
Release files / qcportal-0.12.3.tar.gz
| Download URL | qcportal-0.12.3.tar.gz |
|---|---|
| Size | 105.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13e133f77dd61da76ed717e509c35f056e663bf7cf7d5ace897b0b175125f9d3
|
|
BLAKE2b-256 checksum How to use checksums |
397ce50a7e5d6bebefe9a6ec93da17194138df973fb5a6a5c2d897b2bf988bf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2.post20191203 requests-toolbelt/0.9.1 tqdm/4.39.0 CPython/3.7.5
|
Security for qcportal 0.12.3
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.