QCSC Prefect Adapters
Local process and scheduler adapters for QCSC Prefect workflows. Local commands are executed without a shell or generated job script; scheduler targets use their Jinja2 script templates.
Slurm single-job execution uses a matching scontrol record while the controller
retains the job. Pending and running jobs do not require Slurm accounting.
sacct remains the fallback when the record is absent or scontrol fails;
transient scheduler failures are retried until the configured timeout.
This does not add historical recovery after a job is purged. Bulk monitoring
continues to use sacct.
1 maintainer
Metadata
1 maintainer
Release files for qcsc-prefect-adapters 0.3.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 | Actions |
|---|---|---|---|---|
| qcsc_prefect_adapters-0.3.0.tar.gz | 22.6 kB | With provenance | Details for qcsc_prefect_adapters-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qcsc_prefect_adapters-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for qcsc_prefect_adapters-0.3.0-py3-none-any.whl |
Total release size: 45.9 kB
Release files / qcsc_prefect_adapters-0.3.0.tar.gz
| Download URL | qcsc_prefect_adapters-0.3.0.tar.gz |
|---|---|
| Size | 22.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b760a78ee6450baa321ea5370af55bf0282e41c1c20002bc1bd372d6aff27596
|
|
BLAKE2b-256 checksum How to use checksums |
f87fdd008f08a3aff5ff7021ce924ad4a3fcff6df9df37e19f6976bf50bddc7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / qcsc_prefect_adapters-0.3.0-py3-none-any.whl
| Download URL | qcsc_prefect_adapters-0.3.0-py3-none-any.whl |
|---|---|
| Size | 23.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a26f370234ea173068fe0f6a3d16bd5ea4a5cecfd251b8ad4cf5b8243b92e16f
|
|
BLAKE2b-256 checksum How to use checksums |
6316f7db6674723862e912affaad15d0248c3037a88fcb2833ee15e67ad82969
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for qcsc-prefect-adapters 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qcsc_prefect_adapters-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
