Skip to main content

Logo

Polypus

A distributed quantum computing library — Rust core, Python bindings, one API across simulators and real QPUs.

CI status License: EUPL-1.2 Python 3.8+ Documentation Status: active development

Table of Contents

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.1) and is published on PyPI as polypus-quantum — pip install polypus-quantum (it imports as polypus). See Installation.

Key Features

  • Multi-QPU execution — run any Qiskit QuantumCircuit, a native polypus.Circuit, or an OpenQASM 2.0 string, and automatically split shots across n_qpus to 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's assign_parameters and GIL-free, so concurrent evaluation threads bind candidates truly in parallel.
  • A real Cargo workspace, not a monolith — circuits, simulator, optimizers, cost observables, physics layer, execution backends, orchestration, evaluation, and logger are independent, individually testable crates; the pure-Rust ones have no Python dependency and are usable from any Rust project.

Quickstart

Same project, three names — pip install polypus-quantum · import polypus · cargo add polypus. See Installation.

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

Same project, three names — pip install polypus-quantum · import polypus · cargo add polypus. The name polypus on PyPI is taken by an unrelated project, so the Python distribution is published as polypus-quantum; the Python import name and the Rust crate both stay polypus.

The recommended way to install Polypus is from PyPI:

pip install polypus-quantum

Then import polypus (see Quickstart). CUNQA and the QMIO real-QPU backend are optional extras — see CUNQA below and the from-source build for --features qmio.

From source

To build from a checkout — for contributors, or to enable the qmio backend — use 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 develop installs only the compiled polypus extension, not the bundled polypus_python helpers. 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_parameters and, crucially, GIL-free — concurrent evaluation threads bind candidates truly in parallel (see benchmarks/bench_native_vs_qiskit.py).
  • Batched simulation: the local backend submits each evaluation batch (e.g. a whole DE population) in a single AerSimulator.run call with max_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 (see benchmarks/bench_batching.py). Distributed backends cap each wave's concurrency at n_qpus via their QuantumBackend::capabilities (BackendCapabilities::max_concurrency), which the Planner enforces.
  • Native circuits shine brightest with backends that consume OpenQASM directly (e.g. CUNQA), where the Qiskit re-parse disappears entirely.
  • Automatic gate-parallel calibration: the native (backend="polypus") statevector simulator switches its gate kernels to the parallel path at a machine-specific qubit count. The first import polypus on a machine measures that crossover once (well under a second) and caches it under $XDG_CACHE_HOME/polypus/ (or ~/.cache/polypus/); every later import reuses the cache with no measurement. This runs on the real runtime hardware, so pip install polypus-quantum wheel users get a tuned threshold with no manual step. It fails safe — a read-only cache dir (containers/CI) falls back to the default threshold without error, and correctness is never affected. Set POLYPUS_NO_AUTOCALIBRATE=1 to skip it entirely (CI, containers, reproducibility runs); you can also tune it explicitly at any time with polypus.calibrate_parallel_threshold().

Project Architecture

Polypus is a Cargo workspace of focused crates plus one Python package:

Path Language Role
crates/polypus Rust + PyO3 The Python extension module and PyO3 edge: #[pyclass]/#[pyfunction] bindings, the typed polypus.* exception hierarchy, and re-exports of the workspace crates
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-observable Pure Rust Native, GIL-free cost observables (QUBO / Ising and other diagonal costs) mapping measurement counts to per-candidate expectation values, parallelized with rayon
crates/polypus-physics Pure Rust Classical Monte Carlo transport and quantum Hamiltonians expressed as Pauli sums
crates/polypus-infrastructure Rust + PyO3 Execution backends (local Aer, native, CUNQA, QMIO) and the Planner that sizes and runs circuit waves — how a circuit executes
crates/polypus-orchestration Pure Rust Flow/Scheduler/Resources policy and optimizer dispatch — how a flow is orchestrated; deliberately pyo3-free
crates/polypus-evaluation Rust + PyO3 The oracles (VqcOracle, QmlOracle, variance) and their OracleFactory assembly — how a candidate is evaluated
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, crates/polypus-infrastructure and crates/polypus-evaluation link against Python (via PyO3); every other Rust crate is dependency-free with respect to PyO3 and can be used standalone from any Rust project.

Documentation

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 Pérez González, Kevin and Sendón Caamaño, Uxía and {Galicia Supercomputing Center (CESGA)}},
  title   = {{Polypus: A Distributed Quantum Computing Library}},
  year    = {2026},
  url     = {https://github.com/Bahia-Software/polypus},
  doi     = {PENDING},  % PENDING: Zenodo concept DOI once the first release is archived (see docs/RELEASING.md)
  version = {0.7.1}
}

Credits

  • Diego Beltrán Fernández Prada
  • Víctor Sóñora Pombo
  • Sergio Figueiras Gómez
  • Miguel Boubeta Martínez
  • Kevin Pérez González
  • Uxía Sendón Caamaño
  • 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.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for polypus-quantum 0.7.1
File Size Uploaded
polypus_quantum-0.7.1.tar.gz 324.1 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for polypus-quantum 0.7.1
File
polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl PyPy 3.11 PyPy 3.11 7.3 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl PyPy 3.11 PyPy 3.11 7.3 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl PyPy 3.10 PyPy 3.10 7.3 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl PyPy 3.9 PyPy 3.9 7.3 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details
polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details
polypus_quantum-0.7.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details
polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
polypus_quantum-0.7.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details
polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details
polypus_quantum-0.7.1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details
polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64 Details
polypus_quantum-0.7.1-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details
polypus_quantum-0.7.1-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details
polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.17+ x86-64 Details
polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.17+ ARM64 Details

Total release size: 23.9 MB

Release files / polypus_quantum-0.7.1.tar.gz

Download URL polypus_quantum-0.7.1.tar.gz
Size 324.1 kB
Tags Source
SHA-256 checksum
How to use checksums
855213d26aa06e3520dd248ed1774670d1bb50fab72189e83a3076b147f381d5
BLAKE2b-256 checksum
How to use checksums
2534c72cdfc8357e0a8e25845b9ae352ce23846551a9906fae615f9e4128c97b
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 929.5 kB
Tags Linux glibc 2.17+ x86-64 PyPy 3.11 PyPy 3.11 7.3
SHA-256 checksum
How to use checksums
e6086d341a77f3aec5108542d6a97c3919a52beb60780360b6920f246c93c931
BLAKE2b-256 checksum
How to use checksums
a790363fba123c40c12853146b9e3e3f80b7a2307d8ab6ef548e4b4960a8b35a
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-pp311-pypy311_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 932.5 kB
Tags Linux glibc 2.17+ ARM64 PyPy 3.11 PyPy 3.11 7.3
SHA-256 checksum
How to use checksums
a88f88b3f7e4bdcec7279c74f2e2783588e475909c34b180f5c228585d511520
BLAKE2b-256 checksum
How to use checksums
f0b12aaaf3f41778340cd37bda628c548396ba704082b08980228b94d9522c64
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-pp310-pypy310_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 932.9 kB
Tags Linux glibc 2.17+ ARM64 PyPy 3.10 PyPy 3.10 7.3
SHA-256 checksum
How to use checksums
48655f1ea7632b41e9e9d861a6cd6e9969504d9494301c6e726609ccdf7ddfad
BLAKE2b-256 checksum
How to use checksums
94cd4006e51b17f39040ea5019ebc6775b34f50053937ea6532b097704f9e471
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-pp39-pypy39_pp73-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 933.8 kB
Tags Linux glibc 2.17+ ARM64 PyPy 3.9 PyPy 3.9 7.3
SHA-256 checksum
How to use checksums
57da0cadd672b671ddb0e5c1760975f1534c779032a4339f0120f8a7af64e532
BLAKE2b-256 checksum
How to use checksums
546164456ac0f8284fd9e64ddcfb9440820118b2f596b1c10543ff923c93ed77
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 910.6 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
e1fbf1115725270ca9e20c0be1814a3f8f4db3d4e8953bca47060d33793026a1
BLAKE2b-256 checksum
How to use checksums
26a9e295bcd091d840e20241f75e892828054a90e8f30d233fb2979fbead4502
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 915.7 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
9510f37cb295bc57cdba202fc66587fb140cd080d3278123a891c1fcc4f082f1
BLAKE2b-256 checksum
How to use checksums
56a3fe1b85a4bd485324080a9c18bf337ff8eb03f4e030c0b3e3248afbf2e65c
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 924.1 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
83956146c75b1030146d74f1c2797e5ea672b620f0123ab508f43a9bf971f9bf
BLAKE2b-256 checksum
How to use checksums
dc684697cbe37b18aa02683e3207d05cc0e4edc1e0b5aecda75b7aab10df8037
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 929.6 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
7648d6991562c4c56fb85351dac9514cd5cbe17bfa500fbaec0278c88c9aec4f
BLAKE2b-256 checksum
How to use checksums
5aa7b7896be583ed2e63bd26ff1ff1721bbe844a35a55d371f5ed9c1277897aa
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp313-cp313-win_amd64.whl

Download URL polypus_quantum-0.7.1-cp313-cp313-win_amd64.whl
Size 705.9 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
f79b46879a597bf31f546f5c7fadc082fe4dc45129989d92da60c93583ec94ae
BLAKE2b-256 checksum
How to use checksums
d577f3239ce231e2fe21e47e843d4557b5667c076d35ff663df75cfd8cf3755e
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 924.8 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
4702e8507450ffdcc5b0ee70bf204a929968623ef302738fe83c9aea72b340ae
BLAKE2b-256 checksum
How to use checksums
4ad4266b5684fd5c3158353f616196daac59ce07881cea6197c6e50b78163a8e
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 928.1 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
3cc0ba0d9a5b38ecb6f126ea6fc1ee4c922fb89890883bc0d2e560b6f2ee955d
BLAKE2b-256 checksum
How to use checksums
cbddc8e90f09d05757b3fdca435a3e5c350e8b9bfab692672915149142a85da1
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp313-cp313-macosx_11_0_arm64.whl

Download URL polypus_quantum-0.7.1-cp313-cp313-macosx_11_0_arm64.whl
Size 833.2 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
9bed54ab3e2738ea4e54dd83e7df0be77f082202b4e8324db3211ea400d338f4
BLAKE2b-256 checksum
How to use checksums
b5024e7822c2de877d42a1e9292832376c9a60395bc96e5a69dbc27d17b96754
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp312-cp312-win_amd64.whl

Download URL polypus_quantum-0.7.1-cp312-cp312-win_amd64.whl
Size 705.8 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
0e9f13439814c9cd31686b378b6cff09a8055eb418d0bcba0c3691545ab2485c
BLAKE2b-256 checksum
How to use checksums
48ae27f5f46b25b83a48006f4c9349e6ccd9985c61bc5d9fbb330d0ff6bfccbd
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 924.9 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
5363b4b0da1c890fdcf5233210224fba4d784c09cdc07b2b2cda8d5480d76037
BLAKE2b-256 checksum
How to use checksums
5f6652926ba1761d93910f98a9ff1f331e86536b9a66124c13a0fdf90d857dbc
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 929.3 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
7a001a0be9793fb9e31fa4635426195f1f00fe8fcd5de5e20cb7344e67dae3b3
BLAKE2b-256 checksum
How to use checksums
92e78ad2d0045b76ae5105b8d9b9e8bb58aa5dc962e6ff7b7059a6b9684854ba
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL polypus_quantum-0.7.1-cp312-cp312-macosx_11_0_arm64.whl
Size 834.1 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
bbae959dd68e0d18d7d819ff829c40a0d5b8cc8ad9529f15c6f69c4a6c96dd7e
BLAKE2b-256 checksum
How to use checksums
b52b740c3aa01982593f269767a56207de13cf70375b788aa8f77a0688a50aa8
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp311-cp311-win_amd64.whl

Download URL polypus_quantum-0.7.1-cp311-cp311-win_amd64.whl
Size 707.5 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
5c4709939ec5d2343a615024a7ad17186edf23094466626ba9091861cb2b7a0f
BLAKE2b-256 checksum
How to use checksums
373c96d7dcb220c0c133843f0f481045448f95adda9398299791476c77e96bfa
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 927.8 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
b1384f84a08149e9fbe70ad822eb5f936cd17bec0930f924ee57b096a3922fde
BLAKE2b-256 checksum
How to use checksums
ead62da664b8ae17191ff6cc0dc7f9dd60c71a962ff7c69f78e99c32a5904c00
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 931.9 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
0b2a5c707f677631fca4843cea35864510f22e78fd9fd52cc1a88fe8335a81dc
BLAKE2b-256 checksum
How to use checksums
a0027357b081e91a55a6da1c8735729bd70a0750040dfe3ba0d1ace8f3404bff
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL polypus_quantum-0.7.1-cp311-cp311-macosx_11_0_arm64.whl
Size 843.3 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
61bd85d05b975fb2704179a4df40d722e0a82d28e9a1b7b769924b0a6fefac8f
BLAKE2b-256 checksum
How to use checksums
167632061592c655f4c60e7fc22504aea4edbd55fa1f3e239a0bdf91c30424d8
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp310-cp310-win_amd64.whl

Download URL polypus_quantum-0.7.1-cp310-cp310-win_amd64.whl
Size 707.4 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
e67999e0844d17a062cab5e0dd34e3339ad497bacc69026abe7aa04fd40f4fe4
BLAKE2b-256 checksum
How to use checksums
8bd40864f7e450dc348accd3a7ee39d0386013821d22962aaa03bf0a2e8eba55
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 927.6 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
310d301b37a05a833e374e95a65e6b8b482ec9a6e4f6d18791d4d307370a920c
BLAKE2b-256 checksum
How to use checksums
c5e6b4ec30aa679c1abe8a3830367e741a4189b3f381acc502d06c01c494a52b
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 932.3 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
6c024c4cc2619ce04f04c3b6650d79465a6d240ac34dd9a32f354408f54b05a2
BLAKE2b-256 checksum
How to use checksums
ee07e743cda824fafb24043917830d45ee1772d93eb5563b21fac2642f629388
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp310-cp310-macosx_11_0_arm64.whl

Download URL polypus_quantum-0.7.1-cp310-cp310-macosx_11_0_arm64.whl
Size 843.6 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5c3a8305b37e7d229ee4f0bb929e6cf88645d0df5dc0d24d71ec95914d359532
BLAKE2b-256 checksum
How to use checksums
e13bd6eb21bdc35ceba1ff5ab69babc274bfadd0206ab22df7c4d109c4fbe0d3
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp39-cp39-win_amd64.whl

Download URL polypus_quantum-0.7.1-cp39-cp39-win_amd64.whl
Size 707.5 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
8861528c3d9bb4f254cc68c3df1eb2a39e381948d76caea1268431e093f65115
BLAKE2b-256 checksum
How to use checksums
ac9e313c4de8731edb1c08f6698cdadac17c2c24f6cc145ae7d573abb6e2a85d
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 928.3 kB
Tags CPython 3.9 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
5a8b19b48fa0f6eeeeb353586d32fcbd32be11dca79affffb0b35526cebd6b31
BLAKE2b-256 checksum
How to use checksums
8eeaefa63a35b70ea60924cac4b96bf7fc42e2eacc4ba881ada374c7d9c6366a
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 23, 2026.

Transparency log

Release files / polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL polypus_quantum-0.7.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 932.4 kB
Tags CPython 3.9 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
9e312537c5884d34d45a2348da587ecca1c352aa5f38cef36a67e94d0c779e10
BLAKE2b-256 checksum
How to use checksums
9438c38c139d4791286eed9726cd0b824506f33a3df3b0f6beff40b7642346e9
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 23, 2026.

Transparency log

Release history Release notifications | RSS feed

0.7.2

20 release files

This release

0.7.1 This release

28 release files

0.7.0

28 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page