runningman
runningman is a Qiskit Runtime interface that aids in building vertically and maintaining a platform agnostic interface.
About
Executing on IBM Quantum systems is now done through the Qiskit Runtime, and the ubiqitous backend.run() will be removed from their service. For those looking to build on top of Qiskit this has several consequences. First, supporting multiple hardware providers is now more complicated, and boilerplate code must be written to handle differing interfaces. Second, for packages that require backend knowledge, e.g. for things like error suppression and mitigation techniques, one must either carry two pieces of information around (backend instance and Runtime executor for IBM systems) or use the executor in place of a backend and extract the details from there. This would again require a bit of machinery to do this; code that would have to be reproduced for each package / repo that needs it.
runningman is a package that takes care of a lot of this machinery in a single location. Its primary goal is to enable backend.run() to work on IBM Quantum systems via a wrapper; once again allowing for the backend to be the sole variable needed for getting device characteristics as well as performing the execution, and making it easier to work across providers that leverage Qiskit.
Usage
See the tutorials folder.
Metadata
Release files for runningman 2.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 | |
|---|---|---|---|---|
| runningman-2.3.0.tar.gz | 15.2 kB | Without provenance | Details |
Release files / runningman-2.3.0.tar.gz
| Download URL | runningman-2.3.0.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99f98ca2c854363083c5a39d2382667f6eed36a8e1db312d4ff0918f417290d7
|
|
BLAKE2b-256 checksum How to use checksums |
58da1844e876e56efcd015fe0d76a929a457722531ed77b4c133352bb748bd93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.6
|
Security for runningman 2.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.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.