This release is a pre-release and may not be stable for production use.
qdash-sdk
qdash-sdk provides qdash.sdk: the QDash session, which validates and starts calibrations
on a chip and lists and runs the workflows registered in a project, and the calibration
definitions, built on
qdash-client. Installing it installs the matching
qdash-client release:
pip install qdash-sdk
from qdash.sdk import QDash
with QDash.from_env() as qdash:
# A registered workflow runs code saved in QDash on the chip it was saved for.
for summary in qdash.workflows.list():
print(summary.name, summary.chip_id)
workflow = qdash.workflows.get("coherence_check")
result = workflow.run(parameters={"qids": ["0", "1"]}).wait()
print(result.status)
qdash.scripts and qdash.dashboards save metric scripts and dashboards; a session works
without with too:
from qdash.sdk import Dashboard, QDash, Script
qdash = QDash.from_env()
script = qdash.scripts.create(Script.from_file("zx90_median.py", visibility="project"))
board = Dashboard("ZX90 health", visibility="project")
board.add_metric(script.metric("zx90_median"), period=14)
print(qdash.dashboards.create(board).dashboard_id)
The Python client guide covers configuration,
chip.calibrate(targets, steps), which runs steps defined in Python on the chip you name,
registered workflows, the pipeline API, and metric scripts and dashboards.
Develop the Package
Install the workspace and run the SDK checks from the repository root:
uv sync --all-groups --all-packages
task test-sdk
src/qdash/sdk/ holds the SDK sources; API requests, models, configuration, and errors stay in
qdash-client. tests/test_sdk_distributions.py builds both wheels and checks that each one
installs only its own namespace.
Version and Publication
qdash-sdk has no version of its own. hatch-vcs derives it the same way as qdash-client,
and hatch_build.py pins the dependency to that version: a build of X.Y.Z or X.Y.ZbN
requires qdash-client==X.Y.Z or qdash-client==X.Y.ZbN. Development builds require any
qdash-client.
.github/workflows/publish-qdash-client.yml publishes both packages from one release record:
qdash-client first, then qdash-sdk. See
Python SDK architecture.
Metadata
Release files for qdash-sdk 1.10.5b1298
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 |
|---|---|---|---|---|
| qdash_sdk-1.10.5b1298.tar.gz | 31.6 kB | With provenance | Details for qdash_sdk-1.10.5b1298.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qdash_sdk-1.10.5b1298-py3-none-any.whl | Python 3 | none | any | Details for qdash_sdk-1.10.5b1298-py3-none-any.whl |
Total release size: 54.3 kB
Release files / qdash_sdk-1.10.5b1298.tar.gz
| Download URL | qdash_sdk-1.10.5b1298.tar.gz |
|---|---|
| Size | 31.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0b725704924212055ff32fa73e5637531b51c0a232c16ea3e882f3095020235
|
|
BLAKE2b-256 checksum How to use checksums |
923c7812ca9b970fa2dac80290feef4ef79be45251ef22f3f52fd643f1e41675
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Nov 21, 2026.
Transparency logRelease files / qdash_sdk-1.10.5b1298-py3-none-any.whl
| Download URL | qdash_sdk-1.10.5b1298-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
891c3d3e242ce563f3c5da4cb300aff15cd4138ed99e9cd5ecc4798b076218b1
|
|
BLAKE2b-256 checksum How to use checksums |
265b2eb3c12a4f02341641eb4a27b4147019d46c190f7ac27dfe11e090844ebc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Nov 21, 2026.
Transparency logSecurity for qdash-sdk 1.10.5b1298
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
Both files in this release have been uploaded with provenance metadata.
Attestation for qdash_sdk-1.10.5b1298.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 Nov 21, 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.