qevedo-simulator
Python bindings of qvd, a fast
quantum circuit simulator written in Rust. It installs as
qevedo-simulator and imports as qevedo.simulator.
pip install qevedo-simulator # add [numpy] for NumPy state vectors
from qevedo.simulator import Circuit, expectation, run, statevector
bell = Circuit(2).h(0).cx(0, 1).measure_all()
result = run(bell, shots=1000, seed=1)
print(result.counts, result.backend) # {'00': ..., '11': ...} stabilizer
# OpenQASM 2 or 3 text works anywhere a circuit does.
result = run("""
OPENQASM 3.0;
include "stdgates.inc";
qubit[3] q;
bit[3] c;
h q[0];
cx q[0], q[1];
ccx q[0], q[1], q[2];
c = measure q;
""", shots=1000)
state = statevector(Circuit(3).h(0).cx(0, 1).t(2)) # NumPy complex128 array
# Expectation values by Pauli propagation, far beyond a state vector:
# a Pauli string, a {string: coefficient} dict or a Qiskit SparsePauliOp.
e = expectation(Circuit(2).h(0).cx(0, 1), {"Z0 Z1": 1.0, "X0 X1": 0.5})
print(e.value, e.truncated_one_norm) # 1.5, and a bound on its error (0)
run chooses the simulation method automatically:
| Backend | For | Scale on one workstation |
|---|---|---|
stabilizer |
Clifford circuits | tens of thousands of qubits |
near_clifford |
Clifford circuits with few non-Clifford gates | hundreds of qubits, ~30 active |
statevector |
anything that fits in memory (AVX2 kernels, gate fusion) | ~32 qubits |
mps |
low-entanglement circuits | 100+ qubits, approximate beyond χ |
Pass backend= to force one. The result reports the method that ran, its
timings, and the MPS fidelity estimate or the near-Clifford peak active
qubits. Simulations release the GIL.
expectation propagates the observable backwards through the circuit
(Cliffords for free, small coefficients dropped), for up to 1024 qubits:
<Z62> of IBM's 127-qubit, 20-step kicked Ising circuit takes 0.25–9.6 s
at the thresholds in the main README's benchmark.
x86-64 wheels are built for AVX2 + FMA processors (2013–2015 or newer); other x86-64 machines can build from source with a Rust toolchain.
License: MIT.
1 maintainer
Metadata
1 maintainer
Release files for qevedo-simulator 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qevedo_simulator-0.1.1.tar.gz | 354.5 kB | With provenance | Details for qevedo_simulator-0.1.1.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| qevedo_simulator-0.1.1-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for qevedo_simulator-0.1.1-cp310-abi3-win_amd64.whl |
| qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details for qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details for qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| qevedo_simulator-0.1.1-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for qevedo_simulator-0.1.1-cp310-abi3-macosx_11_0_arm64.whl |
| qevedo_simulator-0.1.1-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details for qevedo_simulator-0.1.1-cp310-abi3-macosx_10_12_x86_64.whl |
Total release size: 7.7 MB
Release files / qevedo_simulator-0.1.1.tar.gz
| Download URL | qevedo_simulator-0.1.1.tar.gz |
|---|---|
| Size | 354.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b5633231a52772ac6ae8b6c0bd8efcd73e3e32f6c14d8c71afdab367e7ef39a
|
|
BLAKE2b-256 checksum How to use checksums |
6a0ae6c0a59f8c191eef5d4691a687fc8e6e7122192d3d2e819e28ca02402ab6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / qevedo_simulator-0.1.1-cp310-abi3-win_amd64.whl
| Download URL | qevedo_simulator-0.1.1-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
5a3e2d3a3b3613d47dd5536a77a341d267e1559ee7c8cc8d339fb6c6885d96b3
|
|
BLAKE2b-256 checksum How to use checksums |
2011c703b6b10e675832308c1ff35d84caa61ba7172b8b12c871899093ca216f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ae03fd32073e6e2966d6cea31a29d529b86cc694fb36d9ce7aa87697cbbb5c22
|
|
BLAKE2b-256 checksum How to use checksums |
b6bbd1e8a71fc658135c945aa0202af74d5c4af5d9c660135ab759d0a8a8fc56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | qevedo_simulator-0.1.1-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3d5f54c813cc02dd80cb0b66ca9ca9c5c68cdf74272ca1876346128a9e88da9b
|
|
BLAKE2b-256 checksum How to use checksums |
2521e5811aa0f1cf3cdb1a36413f8bababd0c8cf525fa957ff5350b1bcf6383d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / qevedo_simulator-0.1.1-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | qevedo_simulator-0.1.1-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7a3a7762c4857a83c7c32265956b7513839e4084a1d7fc9420b5e66883e88037
|
|
BLAKE2b-256 checksum How to use checksums |
b69a6d5bfd62cf208bdaec0dad31c7c3b7c60bc664cbf990ebf1eaa565ce314c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / qevedo_simulator-0.1.1-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | qevedo_simulator-0.1.1-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
d48554f3fa3290334b6cc680e59fac6cf032a33b26a1f1f99fe26a586b28b77b
|
|
BLAKE2b-256 checksum How to use checksums |
754bc6d1b966c006b8a91c45d96e00b18d7f8e5ee06af7b2243fedec3ad0c8c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for qevedo-simulator 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for qevedo_simulator-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
