Polypus
A distributed quantum computing library — Rust core, Python bindings, one API across simulators and real QPUs.
Table of Contents
- What is Polypus?
- Key Features
- Quickstart
- Installation
- Usage
- Rust-Native Circuits
- Project Architecture
- Documentation
- Citing Polypus
- Credits
- Dependencies
- License
What is Polypus?
Polypus is an open-source distributed quantum computing library: it runs quantum circuits and trains variational quantum algorithms (VQE, QAOA, QML, …) across one or many QPUs — simulated or real — without changing your circuit code. The core is written in Rust for performance and correctness; Python bindings (via PyO3) make it a drop-in accelerator for existing Qiskit workflows.
It is built for researchers and engineers who need to:
- scale shot execution and population-based training across multiple QPUs instead of one,
- swap between a local simulator, CESGA's CUNQA platform, or CESGA's QMIO real QPU without touching algorithm code,
- keep a Python-friendly API while getting Rust-level performance on the hot paths (parameter binding, batched simulation).
Status: Polypus is under active development (current version:
0.7.0) and is not yet published on PyPI. Install from source — see Installation.
Key Features
- Multi-QPU execution — run any Qiskit
QuantumCircuit, a nativepolypus.Circuit, or an OpenQASM 2.0 string, and automatically split shots acrossn_qpusto cut wall-clock time. - Unified variational training — Differential Evolution, Particle Swarm Optimization, and Quantum Natural Gradient behind a single
polypus.train()API; switch optimizers by changing one argument, populations are distributed across QPUs automatically. - Backend-agnostic — local simulation via Qiskit Aer, CESGA's CUNQA distributed QPU platform, and CESGA's QMIO real quantum processor, the last reached through a pure-Rust, GIL-free ZeroMQ client.
- Native circuit engine (
polypus-circuit) — optional pure-Rust circuit representation with OpenQASM 2.0 and QIR export; parameter binding is ~3x faster than Qiskit'sassign_parametersand GIL-free, so concurrent evaluation threads bind candidates truly in parallel. - A real Cargo workspace, not a monolith — circuits, simulator, physics layer, optimizers, and logger are independent, individually testable crates; the pure-Rust ones have no Python dependency and are usable from any Rust project.
Quickstart
git clone https://github.com/Bahia-Software/polypus.git
cd polypus
bash install.sh --no-tests
import polypus
bell = polypus.Circuit(2).h(0).cx(0, 1).measure_all()
result = polypus.run_quantum_circuit(bell, shots=1000, infrastructure="local")
print(result.counts[0]) # e.g. {'00': 512, '11': 488}
See Usage for Qiskit circuits, multi-QPU distribution, and variational training.
Installation
The recommended way to install Polypus is using the provided script:
bash install.sh
This will interactively guide you through installing dependencies, building the wheel, and optionally running the test suite. For non-interactive environments (CI/CD):
bash install.sh --yes # all defaults, run all tests
bash install.sh --no-tests # skip tests
Manual installation
Install development dependencies:
pip install -r requirements-dev.txt
Build and install Polypus — a single wheel bundles the polypus extension and
the polypus_python helper package:
maturin build --release --out dist
pip install dist/polypus_quantum-*.whl
Note:
maturin developinstalls only the compiledpolypusextension, not the bundledpolypus_pythonhelpers. Build and install the wheel (above) to get both import names.
CUNQA
To install CUNQA please refer to the CUNQA GitHub repository.
Usage
Check the examples/ directory for complete, runnable scripts.
Running a Quantum Circuit
Pass the circuit, the number of shots, the infrastructure and the number of QPUs:
result = polypus.run_quantum_circuit(
qc, shots=NUM_SHOTS, infrastructure=INFRASTRUCTURE, n_qpus=1
)
Distributing Shots Across Multiple QPUs
Set n_qpus > 1 to split the shots across available QPUs and reduce execution time:
result = polypus.run_quantum_circuit(
qc, shots=NUM_SHOTS, infrastructure=INFRASTRUCTURE, n_qpus=10
)
When infrastructure="cunqa", two optional kwargs size the SLURM allocation for the distributed QPUs:
| Parameter | Default | Description |
|---|---|---|
nodes |
1 |
Number of SLURM nodes to request (>= 1) |
cores_per_qpu |
2 |
CPU cores allocated per QPU (>= 1) |
result = polypus.run_quantum_circuit(
qc, shots=NUM_SHOTS, infrastructure="cunqa", n_qpus=10, nodes=2, cores_per_qpu=4
)
Both must be >= 1 for "cunqa" (a 0 reaching SLURM is rejected with a ValueError). They are ignored by infrastructure="local" and "qmio", so those calls omit them.
Both calls return a RunResult: result.counts holds the measurement payload — a list[dict[str, int]] for a single QPU, or a single merged dict[str, int] when n_qpus > 1. The manifest fields result.id, result.seed, result.backend and result.infrastructure record the run for logging and replay. Pass seed=... to run_quantum_circuit() for reproducible shot noise on every simulated backend (native "polypus", Aer, and CUNQA's simulated QPUs); result.seed reports the effective seed used (None only for the "qmio" infrastructure, which is real hardware and rejects an explicit seed).
Training Variational Circuits
Polypus optimizes variational quantum circuits via polypus.train(). The optimizer is selected by passing a method object as the second argument. Polypus distributes the population individuals across the available QPUs automatically.
The common parameters for all methods are:
| Parameter | Description |
|---|---|
qc |
Parameterized quantum circuit |
shots |
Number of shots per circuit execution |
n_qpus |
Number of QPUs to use |
dimensions |
Number of variational parameters |
expectation_function |
Python callable that maps a bitstring to a cost value |
infrastructure |
"local" or "cunqa" |
nodes |
Number of nodes (CUNQA only) |
cores_per_qpu |
Cores per QPU (CUNQA only) |
id |
Experiment identifier for logging |
seed |
Optional RNG seed for a reproducible run (default: drawn from OS entropy) |
If CUNQA is not available, set infrastructure="local".
Differential Evolution
result = polypus.train(
qc,
polypus.DE(
generations=MAX_GENERATIONS, population_size=POPULATION_SIZE, tolerance=TOL
),
shots=N_SHOTS,
n_qpus=N_QPUS,
dimensions=2 * layers,
expectation_function=bitstring_to_obj,
infrastructure=infrastructure,
nodes=NUM_NODES,
cores_per_qpu=CORES_PER_QPU,
id=id,
)
train() (and qml.train()) return a TrainResult carrying the full optimization outcome, not just the tuned parameters:
print(result.best_params) # list[float] — the optimized parameters
print(result.best_fitness) # float — cost/fitness at those parameters
print(result.iterations_run) # int — iterations actually run (early-stopping aware)
print(result.converged) # bool — whether the convergence criterion was met
print(
result.seed
) # int — the effective RNG seed; pass it back as seed=... to reproduce the run
Pin reproducibility with the seed keyword (polypus.train(..., seed=42)) or on the optimizer itself (polypus.DE(..., seed=42)); with no seed, one is drawn from OS entropy and reported back in result.seed.
Particle Swarm Optimization
result = polypus.train(
qc,
polypus.PSO(
generations=MAX_GENERATIONS,
population_size=POPULATION_SIZE,
bounds=(0.0, np.pi),
tolerance=TOL,
),
shots=N_SHOTS,
n_qpus=N_QPUS,
dimensions=2 * layers,
expectation_function=bitstring_to_obj,
infrastructure=infrastructure,
nodes=NUM_NODES,
cores_per_qpu=CORES_PER_QPU,
id=id,
)
Quantum Natural Gradient
QNG requires a variance_function callable that estimates the diagonal quantum Fisher information matrix element for each parameter. Default hyperparameters: learning_rate=0.1, finite_difference_step=0.1, tikhonov_reg=0.05.
result = polypus.train(
qc,
polypus.QNG(
variance_fn,
max_iters=MAX_GENERATIONS,
bounds=(0.0, np.pi),
learning_rate=0.1,
finite_difference_step=0.1,
tikhonov_reg=0.05,
),
shots=N_SHOTS,
n_qpus=N_QPUS,
dimensions=2 * layers,
expectation_function=bitstring_to_obj,
infrastructure=infrastructure,
nodes=NUM_NODES,
cores_per_qpu=CORES_PER_QPU,
id=id,
)
Rust-Native Circuits
The repository is a Cargo workspace; polypus-circuit is its pure-Rust quantum circuit crate — no PyO3/Python dependency, so circuits can be built and serialized without the GIL. crates/polypus (the Python extension) re-exports its API as polypus.Circuit. Qiskit circuits remain fully supported; the Rust API is an additional, high-performance path.
From Python
polypus.Circuit is accepted by run_quantum_circuit and train exactly like a Qiskit QuantumCircuit (an OpenQASM 2.0 string also works for run_quantum_circuit):
import polypus
# Fully bound circuit → run directly
bell = polypus.Circuit(2).h(0).cx(0, 1).measure_all()
result = polypus.run_quantum_circuit(bell, shots=1000, infrastructure="local")
# Parameterized ansatz → train (binding happens in Rust, GIL-free)
qaoa = (
polypus.Circuit(4)
.h(0)
.h(1)
.h(2)
.h(3)
.rzz(0, 1, polypus.Param(0))
.rzz(1, 2, polypus.Param(0))
.rzz(2, 3, polypus.Param(0))
.rzz(3, 0, polypus.Param(0))
.rx(0, polypus.Param(1))
.rx(1, polypus.Param(1))
.rx(2, polypus.Param(1))
.rx(3, polypus.Param(1))
.measure_all()
)
result = polypus.train(
qaoa,
polypus.DE(generations=100, population_size=50),
shots=1024,
n_qpus=1,
dimensions=2,
expectation_function=my_cost,
infrastructure="local",
nodes=1,
cores_per_qpu=1,
id="qaoa",
)
From Rust
use polypus_circuit::{ParameterizedCircuit, Param};
let qc = ParameterizedCircuit::new(4)
.h(0).h(1).h(2).h(3)
.rzz(0, 1, Param(0)).rzz(1, 2, Param(0)).rzz(2, 3, Param(0)).rzz(3, 0, Param(0))
.rx(0, Param(1)).rx(1, Param(1)).rx(2, Param(1)).rx(3, Param(1))
.measure_all();
let qasm: String = qc.to_qasm2_with_params(&[0.4, 0.8])?; // OpenQASM 2.0
let qir_ll: String = qc.to_qir_with_params(&[0.4, 0.8])?; // QIR LLVM IR text (.ll)
let qir_bc: Vec<u8> = qc.to_qir_bitcode_with_params(&[0.4, 0.8])?; // QIR bitcode (.bc)
The generated OpenQASM 2.0 uses standard qelib1.inc gate names and is accepted by Qiskit (QuantumCircuit.from_qasm_str) and Aer.
to_qir_bitcode_with_params requires llvm-as available in PATH because Polypus assembles the textual QIR module into LLVM bitcode externally.
From Python, both outputs are also available:
qc = polypus.Circuit(2).h(0).cx(0, 1).measure_all()
qir_text = qc.to_qir() # str (.ll)
qir_bitcode = qc.to_qir_bitcode() # bytes (.bc)
QASM 2.0 Import
Circuit.from_qasm2 is the inverse of to_qasm2 — it accepts the QASM this library exports and Qiskit's qasm2.dumps output (u/p/u1/u2 are canonicalised to u3, swap to its cx decomposition; multiple registers are flattened; constant expressions like pi/2 are evaluated). Parse errors raise ValueError with the offending line number.
import polypus
from qiskit import qasm2
qc = polypus.Circuit.from_qasm2(qasm2.dumps(qiskit_circuit)) # interop
qc = polypus.Circuit.from_qasm2(open("ansatz.qasm").read()) # persistence
qc.rz(1, 0.5).measure_all() # imported circuits are regular builders
Round-trip guarantee (verified by tests): for any circuit produced by this library, export → import → export is byte-identical. The same API exists in Rust as ParameterizedCircuit::from_qasm2.
Performance Notes
- Parameter binding: ~3x faster than Qiskit's
assign_parametersand, crucially, GIL-free — concurrent evaluation threads bind candidates truly in parallel (seebenchmarks/bench_native_vs_qiskit.py). - Batched simulation: the local backend submits each evaluation batch (e.g. a whole DE population) in a single
AerSimulator.runcall withmax_parallel_experiments=0, so Aer's C++ engine runs the experiments in parallel across cores with the GIL released. Measured ~1.4–2.1x end-to-end training speedup vs per-circuit submission, growing with circuit size (seebenchmarks/bench_batching.py). Distributed backends cap each call atn_qpusviaQuantumBackend::max_batch_size. - Native circuits shine brightest with backends that consume OpenQASM directly (e.g. CUNQA), where the Qiskit re-parse disappears entirely.
Project Architecture
Polypus is a Cargo workspace of focused crates plus one Python package:
| Path | Language | Role |
|---|---|---|
crates/polypus |
Rust + PyO3 | Main library and Python extension module: backends, training loop, Python bindings |
crates/polypus-circuit |
Pure Rust | Circuit representation, OpenQASM 2.0 / QIR export — no PyO3, usable from any Rust project |
crates/polypus-sim |
Pure Rust | Statevector simulator consuming polypus-circuit's ConcreteCircuit directly (no OpenQASM round-trip) |
crates/polypus-optimizers |
Pure Rust | DE, PSO and QNG optimizers, decoupled from circuits and Python via EvaluationOracle/VarianceOracle |
crates/polypus-physics |
Pure Rust | Classical Monte Carlo transport and quantum Hamiltonians expressed as Pauli sums |
crates/polypus-logger |
Pure Rust | Shared log::Log sink for the whole workspace |
polypus_python |
Python | Python-side infrastructure glue (backend connectivity, worker processes) used by the extension module; bundled into the polypus-quantum wheel |
Only crates/polypus links against Python; every other Rust crate is dependency-free with respect to PyO3 and can be used standalone from any Rust project.
Documentation
- API reference (generated with
cargo doc, covers the Rust crates and the PyO3 bindings): https://bahia-software.github.io/polypus/ - Runnable, end-to-end scripts:
examples/ - Performance benchmarks and how to reproduce them:
benchmarks/
Citing Polypus
If Polypus is useful in your research, please cite it:
@software{polypus,
author = {Fernández Prada, Diego Beltrán and Sóñora Pombo, Víctor and Figueiras Gómez, Sergio and Boubeta Martínez, Miguel and {Galicia Supercomputing Center (CESGA)}},
title = {{Polypus: A Distributed Quantum Computing Library}},
year = {2026},
url = {https://github.com/Bahia-Software/polypus},
version = {0.7.0}
}
Credits
- Diego Beltrán Fernández Prada
- Víctor Sóñora Pombo
- Sergio Figueiras Gómez
- Miguel Boubeta Martínez
- Galicia Supercomputing Center (CESGA)
Dependencies
Polypus relies on the following Python packages:
| Package | Version |
|---|---|
qiskit |
≥ 2.0 |
qiskit-aer |
≥ 0.17 |
numpy |
≥ 2.0 |
scipy |
≥ 1.13 |
matplotlib |
≥ 3.9 |
networkx |
≥ 3.2 |
cunqa |
≥ 2.3 (optional) |
See requirements-dev.txt and requirements-examples.txt for the full pinned dependency lists.
License
Polypus is licensed under the European Union Public Licence, version 1.2 (EUPL-1.2). See LICENSE for the full text.
Metadata
Release files for polypus-quantum 0.7.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 | |
|---|---|---|---|
| polypus_quantum-0.7.0.tar.gz | 284.7 kB | Details |
Built distributions (wheels)
Total release size: 22.7 MB
Release files / polypus_quantum-0.7.0.tar.gz
| Download URL | polypus_quantum-0.7.0.tar.gz |
|---|---|
| Size | 284.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
268e39aaef30149e52aa8a74ceece9a43ab01ee4c77eaed6fdedd44e168616fc
|
|
BLAKE2b-256 checksum How to use checksums |
2bd259e89325b863b8fba041711a8e5416de367c7e4584b7f11c5c77cfd14af7
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 882.3 kB |
| Tags | Linux glibc 2.17+ x86-64 PyPy 3.11 PyPy 3.11 7.3 |
|
SHA-256 checksum How to use checksums |
842aa6bfa90db708feae2b5e7adbb16496d93ad3949aa461d2053438eb1d3888
|
|
BLAKE2b-256 checksum How to use checksums |
767eafb40cdb171e185904f501d18c615a19d169955fff50b0d78cb1261cbecc
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-pp311-pypy311_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-pp311-pypy311_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 884.4 kB |
| Tags | Linux glibc 2.17+ ARM64 PyPy 3.11 PyPy 3.11 7.3 |
|
SHA-256 checksum How to use checksums |
47711347532382345011776bc822db3ef982f77250ebffe15ec41c5e2daa8e90
|
|
BLAKE2b-256 checksum How to use checksums |
27a5521d1edb3860f0044764be2dba4724dc51ed0dbb3c426d8cb331bf39406b
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 884.7 kB |
| Tags | Linux glibc 2.17+ ARM64 PyPy 3.10 PyPy 3.10 7.3 |
|
SHA-256 checksum How to use checksums |
c5707c9bb2bfaee49220d0bc9e22c9aeaf97a956c272d6a58133e6fa44ecb074
|
|
BLAKE2b-256 checksum How to use checksums |
ff1da0b19f27522910419197e427b84583ad10cf0e0db143caba58a24bfec524
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 885.5 kB |
| Tags | Linux glibc 2.17+ ARM64 PyPy 3.9 PyPy 3.9 7.3 |
|
SHA-256 checksum How to use checksums |
e62403e3dd1ebc751fc4c8c4e88e152f0b016ad4ad093611c1b3f2f075ee4d52
|
|
BLAKE2b-256 checksum How to use checksums |
baf2d00dc704d3dc0c26f5edf70970b393e03f483c2001afa7029413b6cd670c
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 868.5 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
87f64724ec350a1a0a6da97d446fa71cce1e62e7fffb84851fb69c7a7abdfc67
|
|
BLAKE2b-256 checksum How to use checksums |
99169915f70780bde9acacda044ff7957abee1358212c0778ce5fac8320e2c4d
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 870.9 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
1da7607cdd6240ae111f9b69507c8b08a332ab72f2d302ff9b06b23cdd25b908
|
|
BLAKE2b-256 checksum How to use checksums |
b3625ffd67fd085a587540785e975a805896afbb2261adef25c5ee409771678b
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 878.4 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
7f3a7ae78b98a3d88dc1f9c8a47fb2f3aa10190c7c8312e2114387a06d2735f7
|
|
BLAKE2b-256 checksum How to use checksums |
576601411920051db0ac4146e9f9c04aad0a3f7e026d31f854b720f7ae921abd
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 880.6 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
58ee8a7a2570d6a96cea419f292a3e96aaf29ec445a313beeaf751ce6bcc3e3a
|
|
BLAKE2b-256 checksum How to use checksums |
04e5e01b05d9b6ad1fae8ac6599ed9a131b0b2a418f348f2866aa83f1b29149f
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp313-cp313-win_amd64.whl
| Download URL | polypus_quantum-0.7.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 663.9 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
23fe6e583c2ac4300cbae476e9c977b4d9f419ada4a30927685a49a0e76ffe56
|
|
BLAKE2b-256 checksum How to use checksums |
0ba75e92e4ff34fdd5b7003fb50c39f2aff41b96d50bb7081145d5a473df059e
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 876.6 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ace2cf90a3616d4c261071748701c4ec26fdba8a5ed92a1a9d585e04b74b0208
|
|
BLAKE2b-256 checksum How to use checksums |
7c908872a64c9a1860c05b5518b75aa142c6d37e93197de452f9c2cd2a833f20
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 880.5 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
bec998782e3d6be059cc9f01b031846d3a1dbbb358074f412858e6870bcd5a26
|
|
BLAKE2b-256 checksum How to use checksums |
19d9396dbad4198eb88fec0f64a8f6481e95d8763c0db4c7c2775dd5e2dd740c
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | polypus_quantum-0.7.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 792.4 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0a6e1be9736c62fb44dcf67d2b171390cc10a16ead6cecbd9afd6894f78f7b04
|
|
BLAKE2b-256 checksum How to use checksums |
3a5f49e1cebb372ae3db01f1b4d84ba3f2f39aad2436247e7ef58332f1439bd9
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp312-cp312-win_amd64.whl
| Download URL | polypus_quantum-0.7.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 664.2 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3a22844ba7cdfc44597fbf7e427cc4b3ffc80e28caf514dbad80b5109b07b290
|
|
BLAKE2b-256 checksum How to use checksums |
a1239fd34cd5e60aed8ff0924e4fe1026ccd2fc158684e670f8dc2f0e4fd3d8a
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 876.7 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
7e0577aace0c4c03cdffb3822659084b256b3d64082a2a6078e16acb05fe638e
|
|
BLAKE2b-256 checksum How to use checksums |
bdf6aeaa9be1bb7a176b8710f8c4b08300385721adfddde9c15119d55cb0c917
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 881.3 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
235274908dbf06b8f4ef63e9cbda6d44c31fa4aa02c28981b5d20c1141ba6386
|
|
BLAKE2b-256 checksum How to use checksums |
c8b529a6ce75bfcdd8c16a3e3dea97e7042d70534b0566cfced60d58bd53aca1
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | polypus_quantum-0.7.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 793.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4ba099aef90ddf8a0d66e7d75fee7f69c4097ab39fa14ec685c76801d6ddf348
|
|
BLAKE2b-256 checksum How to use checksums |
cd9fdaa82bca3ed10acef76c65af80f49ea9ce05b12f752f93a8f7c265ebb7e3
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp311-cp311-win_amd64.whl
| Download URL | polypus_quantum-0.7.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 668.1 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d56ddfc4f481d889f4994500215e0f65f8f4ae03ca272fb87f096570f6b527e1
|
|
BLAKE2b-256 checksum How to use checksums |
aa648d758f83af65f2d0d62ea3639ae299ad2d6eb8ae9f285c55f417a2dda6f6
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 881.9 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
5e7cec0b0a4ea5da847ae95dda3628bec3adef7a8e6af90aa9179d623dbc9908
|
|
BLAKE2b-256 checksum How to use checksums |
a5e41dd1fa34eda6042a0715549e7dafff5a504e49ec4aa2f1e225a9d4d1272c
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 883.8 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
72becfe41a35c0abb1c0171ea3731af22d9e00e92cd70a90362d3ac116aa05d5
|
|
BLAKE2b-256 checksum How to use checksums |
ebc9763c55f8e367b5195f2af79017c0688f7dbd4f447d63e4de9b6aa4c1edd2
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | polypus_quantum-0.7.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 802.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
416172f2acf579969e54f8e10815f1ecc8dfc90a2b30d4e717f1563f8fa77f7e
|
|
BLAKE2b-256 checksum How to use checksums |
423d67b3c107d173515b2398a672aa2de4b6ddb73a6f2df3a0dec8de29505625
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp310-cp310-win_amd64.whl
| Download URL | polypus_quantum-0.7.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 668.0 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d0ca46eb23368e690747ba0c8d7ca2f1818b98a68d44dd04374478308c08d242
|
|
BLAKE2b-256 checksum How to use checksums |
170cbc15d0432add0a6e27050a6da399d322eb8db61a6e740a894780e178090b
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 881.8 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
3d8c27755cb030ae939c170f5df0f06bf95cefa2a9efde1c5159fddd089ff1ee
|
|
BLAKE2b-256 checksum How to use checksums |
f87dabdd61eaf17e010f002f67de0e8bf0d1b15baaa8b4e32ab90fee494aca33
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 883.7 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
217a9d63a973e7d394900b7728dccb7bd1438e4b1c6fe5f319b7da4421dd9abb
|
|
BLAKE2b-256 checksum How to use checksums |
885ee440cd7347b643081167d0bc5f92bab8582764bb294fcd73534f1c2cbf0c
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | polypus_quantum-0.7.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 802.8 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
27900164f5a013c9966ed3a7e3ae3699b172946829d853abef89be99e4133062
|
|
BLAKE2b-256 checksum How to use checksums |
1ee1d16432635ce5331d34e627c2c5f18410f202b0a34397e140f4aea6746548
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp39-cp39-win_amd64.whl
| Download URL | polypus_quantum-0.7.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 668.3 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
35552d7fdb51ccb9a9733d45f0220b8c8ad8038dd5c95fd0facb65ee167b2852
|
|
BLAKE2b-256 checksum How to use checksums |
12069877ac5b5bc41711278a91243787b78689317350d979f15606bd0ae8d76e
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | polypus_quantum-0.7.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 882.2 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ec1efd16fef182b962fa3fe080fd989cf9155c5498ce3ce8c02fc78fcaa6f6de
|
|
BLAKE2b-256 checksum How to use checksums |
f2796336825934c45664e5bbd0217a96b3ada110b6f909d05d46aff38969d69d
|
| 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 Sep 17, 2026.
Transparency logRelease files / polypus_quantum-0.7.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | polypus_quantum-0.7.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 883.9 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
b63208ef3cbcecbc741957050a1300f227ab3066209ca3a9f820ef2cd2782b0e
|
|
BLAKE2b-256 checksum How to use checksums |
24602467f66c6fdf9288f672000645eacc92c7c90657931b4a69df1de7f66a2f
|
| 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 Sep 17, 2026.
Transparency log