Skip to main content

SymQ

Exact verification of reversible Boolean circuits, with opt-in, explicitly scoped quantum research extensions.

CI Python 3.10+ MIT license

SymQ computes exact algebraic normal forms (ANFs) of X/CX/CCX/MCX reversible circuits and decides their equivalence. It has pure-Python and optional native C/ZDD backends and a separate SAT engine. It also offers opt-in checkers for restricted measurement-assisted quantum programs. Each checker proves one named theorem. SymQ never switches silently between computing output functions, deciding classical equivalence and comparing quantum channels.

Status: experimental research software. The first release is 0.2.0; from it on, the classical core is kept compatible as the stability policy states, and the experimental and research layers carry no promise. SymQ is not a universal quantum-circuit verifier and not a formally verified implementation. Its verification paths do not export independently checkable certificates, except one opt-in research path for a narrow class of phase obligations (proof levels).

Navigate: Quick start · Question → theorem → API · Contextual substitution · Experimental APIs · Proof levels and replay · Installation · Limits · References

Quick start

This example needs only the pure-Python core: no SAT solver and no C compiler.

from symq import Budget, Circuit, check_equivalence

reference = Circuit(3)
candidate = Circuit(3).ccx(0, 1, 2).ccx(0, 1, 2)   # two Toffolis cancel
result = check_equivalence(reference, candidate, backend="sparse", budget=Budget(max_seconds=5))
assert result.equivalent

mutant = Circuit(3).ccx(0, 1, 2)                     # a real difference has a replayable input
different = check_equivalence(reference, mutant, backend="sparse")
assert not different.equivalent
assert reference.run(different.witness) != mutant.run(different.witness)

Wire indices start at zero, and controls come before the target (ccx(c1, c2, target)). Integer inputs are read least-significant bit first. From the command line, symq check left.qasm right.qasm decides the same question and symq anf circuit.qasm prints the exact output polynomials. Importers accept only strict subsets: symq.qasm.parse_qasm takes reversible OpenQASM 2/3 and rejects measurements and classical control; symq.kickmix.load_kmx takes Qualtran kickmix text, including HMR programs.

Question → theorem → API → limits

Start from the statement you want proved, not from the fastest-looking backend.

Question Theorem proved on success Entry point Main limits
What are the exact output functions? Exact ANF of every output wire make_algebra + simulate + to_anf ANF size can be exponential; backend width caps (backends)
Are two complete reversible circuits equal? Every output agrees on every Boolean input; a difference carries a replayed witness check_equivalence, symq check Classical permutations only
Are selected outputs equal under constants, restored wires or input assumptions? SAT/UNSAT of that declared classical contract symq.sat.Contract + check_sat_equivalence Budget may end inconclusive; no ANFs, no exported UNSAT certificate
Is a replacement valid at one site of a larger circuit? Contextual classical substitution: domain, prefix, interface and suffix obligations symq.labs.contextual_substitution.check_substitution, symq rewrite Sufficient, not complete; says nothing about quantum behaviour
Is a ±1-phase/HMR program a clean, outcome-independent rewrite? Strict branch equality under O1/O2 symq.phase.check_phase_equivalence Restricted grammar; O1/O2 must hold
Do two restricted HMR programs implement the same full or reduced channel? Equality on all coherent input pairs under an explicit physical frame symq.experimental.verify + VerificationContract Two Boolean variables per data bit; width caps
Do recorded measurement outcomes also agree? Equality of the observed instrument Experimental instrument theorem, hybrid-exact Bounded oracle; small programs
Does a reversible loader XOR an exact lookup table into its targets? For every legal address and target, on the coherent span: output = input ⊕ T[address] symq.experimental.check_table_xor X/CX/CCX/MCX only; ≤ 16 address and target bits

The first four rows are statements about classical Boolean functions. The table-XOR contract proves a basis permutation, which extends to the coherent span because the accepted gates have no phases. The three HMR rows have quantum semantics and are not interchangeable with classical equivalence. Channel equality does not imply equal measurement records, and equality after tracing does not imply full-output equality.

symq.verify(left, right, theorem=..., engine=...) routes each theorem to its owning engine. It never chooses a theorem or an engine for you. The result has outcome, reason, witness and certified. equivalent and different are true only for a proved equivalence or difference; both are false for inconclusive and unsupported.

A classical SAT contract

from symq import Budget, Circuit
from symq.sat import Contract, check_sat_equivalence

left = Circuit(3).ccx(0, 1, 2).ccx(0, 1, 2)
right = Circuit(3)
contract = Contract(observed_outputs=(0, 1), restored_wires=(2,))
verdict = check_sat_equivalence(left, right, contract, budget=Budget(max_seconds=10))
assert verdict.outcome == "equivalent"

A restored wire must return to its own original value, even when it is borrowed or dirty. An ignored wire is not implicitly restored.

Contextual substitution

A contextual rewrite replaces the gates in [start, stop) and asks whether the replacement is valid at that site. The prefix may establish facts, such as a clean scratch wire, that make the replacement valid there but not elsewhere.

from symq import Circuit
from symq.labs.contextual_substitution import SubstitutionContract, check_substitution
from symq.labs.rewrite import Weights

# Given the declared input q2 = 0, the first two gates leave q2 clean,
# so CX(q2, q0) at position 2 is the identity there.
source = Circuit(3).cx(0, 2).cx(0, 2).cx(2, 0).cx(0, 1)
contract = SubstitutionContract(initial_constants=((2, 0),), clean_at_cut=(2,))
result = check_substitution(source, (2, 3), Circuit(3), contract=contract,
                            weights=Weights.from_mapping({"cx": 3}))
assert result.equivalent and result.cost.weighted_delta == -3

# Without the declared input, the clean cut cannot be established: refused, never trusted.
refused = check_substitution(source, (2, 3), Circuit(3),
                             contract=SubstitutionContract(clean_at_cut=(2,)))
assert refused.outcome == "precondition_failed" and refused.candidate is None

From the command line, the same work is a four-step workflow, run here from a checkout with the provided examples:

symq locate examples/locate/source.json examples/locate/reference.json --theorem classical
symq prepare-rewrite examples/prepare/source.json examples/prepare/original.json \
  examples/prepare/candidate.json --contract examples/prepare/contract.json \
  --weights examples/prepare/weights.json --output-dir prepared
symq rewrite prepared/request.json --report prepared/proof.json
symq replay prepared/proof.json
  1. locate finds the unique exact occurrence of a small block and its wire map. It proves nothing.
  2. prepare-rewrite turns a small original/replacement pair into a full-width request in a new directory. It is strictly preparatory: its output says ready_for_proof, proved=false, candidate_authorized=false. It never replaces an existing path, and preparation.json is an advisory record of the emitted file hashes.
  3. rewrite proves (or refuses) the substitution and writes a report.
  4. replay recomputes the proof from the embedded request and refuses an edited report.

The cut predicate contains only what the contract declares. The theorem is therefore sufficient but not complete: a valid rewrite can be not_proved when its justification was not declared. A rewrite checker never reports a proved difference, because a local counterexample need not be reachable from the global input. These checkers live in symq.labs, which carries no API promise. See the rewrite guide.

Experimental APIs

SymQ has three installed layers and one development-only layer. None of them silently replaces another.

Layer Contents Promise
symq Circuits, algebras, classical equivalence, SAT contracts, verify facade, CLI Kept compatible as the stability policy states, from the first release; changes are recorded in the changelog
symq.experimental Restricted HMR channels and instruments, coherent domains, prepared references, serialization Installed, opt-in; explicit theorem, frame and backend required. No API promise
symq.labs Contextual rewrites and their preparation, phase certificates, the LRAT proof path, research prototypes (index) No API promise; may change or disappear
formal/ Lean 4 projects checked in development CI (formal runtime model, LRAT gate lemmas) Not installed, never imported by SymQ; Lean is not a runtime dependency

A restricted HMR channel check:

from symq.experimental import VerificationContract, verify
from symq.phase import PhaseProgram
from symq.resources import Budget

reference = PhaseProgram(2, 1)
candidate = PhaseProgram(2, 1).ccx(0, 1, 2)
event = candidate.hmr(2)
candidate.cz_if(event, 0, 1)
contract = VerificationContract(theorem="full_channel", backend="zdd")
assert verify(reference, candidate, contract, budget=Budget(max_seconds=10)).equivalent

A table-XOR loader check, from the opt-in experimental API:

from symq import Circuit
from symq.experimental import TableXorContract, check_table_xor

loader = Circuit(6).cx(0, 2).cx(1, 2).cx(1, 3)
contract = TableXorContract(
    width=6, address_wires=(0, 1), target_wires=(2, 3), clean_wires=(4,),
    borrowed_wires=(5,), table=(0, 1, 3, 2), legal_addresses=(0, 1, 2),
    target_values=None, table_id="t0", slot_id="s1", theorem="coherent",
)
assert check_table_xor(loader, contract, backend="exhaustive").equivalent
faulty = check_table_xor(Circuit(6).cx(0, 2).cx(1, 3), contract, backend="exhaustive")
assert faulty.status == "different" and faulty.witness is not None

See the table-XOR API guide for receipts and replay.

The HMR channel quantum input is arbitrary coherent data plus explicitly zero-prepared ancillas. A general Hadamard, rotation or reset program is not accepted by this sign-phase checker. The hybrid and cyclotomic reference engines have their own grammars. See the experimental guide, phases and composition.

Proof levels and replay

A positive answer is only as strong as the step that produced it. SymQ keeps these levels apart:

Level What it establishes Where
Engine decision SymQ computed equivalent for the declared theorem; trust rests on the engine (and on the SAT solver for SAT routes) Every checker
Replayed witness A claimed difference reproduces on concrete inputs, outside the symbolic engine Classical, table-XOR and channel differences
Replayed report A stored JSON report is recomputed from its embedded request; stored and fresh decisive results must match exactly symq replay, replay_table_xor
Independently checked formula proof For one opt-in research path (factored phase certificates), the obligation is encoded as a CNF and its UNSAT proof is exported as LRAT. A small standalone checker verifies it against a pinned CNF without a SAT solver, and a consumer rebuilds that CNF from the sources. In development CI, Lean's verified LRAT checker also proves selected instances. This certifies that CNF, not the source-to-CNF encoding or the quantum semantics symq.labs.lrat_rup, phase_proof_bundle, lrat_lean (details)
Lean theorems about an abstract model General theorems on Tseitin clauses, acyclic DAG evaluation, UNSAT soundness of the solver query shape and ripple-carry addition. Their statements and the model definitions are restated in checked contract files, so a weakened statement fails the build. They describe a model, which tests compare with the Python code formal/, development CI only (details)
Formal proof of SymQ itself Machine-checked correctness of the Python/C runtime or of its quantum semantics No

Passing tests, a green CI run or an agreeing second engine are evidence, not formal proof. A JSON receipt authorizes nothing until it is replayed. Its provenance (input-file digests, execution data) stays historical metadata that replay cannot authenticate.

Installation

Python 3.10 or newer. A released version installs from PyPI:

python -m pip install symq          # add "symq[sat]" for the SAT engine

CPython 3.10 to 3.14 on Linux (x86-64 and arm64, glibc and musl) and on macOS (Intel and Apple silicon) get a wheel with the native C core. Everything else, Windows and free-threaded CPython included, gets the pure-Python package: the verdicts are the same, but the native engines are absent (--engine native is refused, auto uses the pure-Python zdd), so a budget can run out where the native core would have concluded. python -m symq doctor says which one is installed. For development, install from a source checkout:

git clone https://github.com/yoch/symq.git
cd symq
python -m venv .venv
source .venv/bin/activate
python -m pip install -e .
Installation Adds
python -m pip install -e ".[sat]" PySAT, for SAT contracts and contextual rewrites
python -m pip install -e ".[dev]" Tests, Ruff, mypy and the SAT development dependencies
python -m pip install -e ".[dev,external]" Optional PolyBoRi, CUDD and MQT QCEC comparison adapters
python -m pip install -e ".[test,crosscheck]" MQT QCEC alone, at the version the required cross-check job uses
Platform Native C core What CI runs on every change
Linux (x86-64) yes Whole suite on CPython 3.10 to 3.14; sanitizers; the cross-check against MQT QCEC
macOS (Apple silicon runner) yes Core tier on CPython 3.12
Windows (x86-64) no: pure Python only Core tier without the native tests on CPython 3.12

The core tier is the tests of symq, symq.sat, symq.backends, the repository guards and the runnable examples of the documentation; the tests of the experimental and research layers run on Linux only.

The native C/ZDD extension is optional. From a checkout or a source distribution it builds at install time when a compiler and the Python headers are present; a wheel from PyPI either contains it or does not. python -m symq doctor reports whether it loaded and why not. See getting started.

Limits

  • Exact does not mean unbounded. Unsupported gates, malformed contracts and exhausted budgets are refused or end inconclusive. An unfinished computation never establishes a difference, and inconclusive or unsupported is never turned into a proof.
  • Proof boundaries matter. Classical output equality is not channel equality. A channel that forgets outcomes is not an observed instrument. A dirty ancilla is never silently initialized to |0>.
  • Decomposition needs a proof. check_equivalence_by_blocks splits only classically disconnected circuits; a connected circuit is not decomposed without a separately proved interface contract.
  • Budgets are engine-specific. Term and node limits measure different data structures. A cooperative deadline is not an isolated-process limit, and max_bytes is not a process memory cap. See resource contracts.
  • Performance claims need matched tasks. Deciding equivalence, exporting ANFs and checking instruments are different jobs. No backend wins on every circuit; recorded measurements describe specific commits and workloads (evidence).

Documentation

Topic Document
First steps, native core Getting started, glossary, index
Backends, orders, blocks Backend guide
SAT contracts and relational cuts SAT guide
Contextual rewrites, preparation and replay Rewrite guide
Table-XOR loader contracts Public API, contract guide
Research modules, LRAT proofs, Lean model Labs index
HMR semantics HMR specification
Runnable scripts and CLI inputs examples/ (the Python scripts run in the test suite; the JSON inputs are exercised by CI), demo
Architecture, archive, history Architecture, archive index, changelog
Contributing and security CONTRIBUTING.md, code of conduct, AGENTS.md, SECURITY.md
Licenses of redistributed test and benchmark inputs Third-party notices

References

  • S. Minato, Zero-suppressed BDDs for set manipulation in combinatorial problems, DAC 1993: the monomial-set representation behind the ZDD backends.
  • A. Ignatiev, A. Morgado, J. Marques-Silva, PySAT: A Python toolkit for prototyping with SAT oracles, SAT 2018 (PySAT): the SAT engine.
  • L. Burgholzer, R. Wille, Advanced equivalence checking for quantum circuits, IEEE TCAD 2021 (MQT QCEC): the optional comparison adapter.
  • Qualtran (Apache-2.0): source of the pinned kickmix fixtures (provenance).
  • L. Cruz-Filipe, M. Heule, W. Hunt, M. Kaufmann, P. Schneider-Kamp, Efficient certified RAT verification, CADE 2017: the LRAT proof format.
  • L. de Moura, S. Ullrich, The Lean 4 theorem prover and programming language, CADE 2021: the proof assistant used in formal/.

Development

python -m pip install -e ".[dev]"
ruff check .
mypy
python -m pytest -q

SYMQ_TEST_REQUIRE=native,sat turns the skips of native- and sat-marked tests into errors. Changes should state their accepted grammar and theorem, add differential and adversarial tests, keep concrete witnesses, and report negative results with exact source and environment fingerprints.

MIT licensed · Research software · No general-purpose quantum certification claim.

Metadata

Release files for symq 0.2.0

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

Source distribution (sdist)

Source distribution for symq 0.2.0
File Size Uploaded Provenance Actions
symq-0.2.0.tar.gz 1.5 MB With provenance Details for symq-0.2.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for symq 0.2.0
File Actions
symq-0.2.0-py3-none-any.whl Python 3 none any Details for symq-0.2.0-py3-none-any.whl
symq-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for symq-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl
symq-0.2.0-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details for symq-0.2.0-cp314-cp314-musllinux_1_2_aarch64.whl
symq-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.2.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.2.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.2.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for symq-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
symq-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.15+ x86-64 Details for symq-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl
symq-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for symq-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl
symq-0.2.0-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details for symq-0.2.0-cp313-cp313-musllinux_1_2_aarch64.whl
symq-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.2.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.2.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.2.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for symq-0.2.0-cp313-cp313-macosx_11_0_arm64.whl
symq-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for symq-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
symq-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for symq-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl
symq-0.2.0-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details for symq-0.2.0-cp312-cp312-musllinux_1_2_aarch64.whl
symq-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.2.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.2.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.2.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for symq-0.2.0-cp312-cp312-macosx_11_0_arm64.whl
symq-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for symq-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
symq-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for symq-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl
symq-0.2.0-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details for symq-0.2.0-cp311-cp311-musllinux_1_2_aarch64.whl
symq-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for symq-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.2.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for symq-0.2.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.2.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for symq-0.2.0-cp311-cp311-macosx_11_0_arm64.whl
symq-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for symq-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
symq-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for symq-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl
symq-0.2.0-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details for symq-0.2.0-cp310-cp310-musllinux_1_2_aarch64.whl
symq-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for symq-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.2.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for symq-0.2.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.2.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for symq-0.2.0-cp310-cp310-macosx_11_0_arm64.whl
symq-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for symq-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl

Total release size: 18.4 MB

Release files / symq-0.2.0.tar.gz

Download URL symq-0.2.0.tar.gz
Size 1.5 MB
Tags Source
SHA-256 checksum
How to use checksums
c5a2b46c4d8e18cff41ad73561db4b44c41421e3ca1692f16d456c242c66d420
BLAKE2b-256 checksum
How to use checksums
ab87438d2f422dc62586e158e9687d529e06770a3a159ab42a06b60471071702
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-py3-none-any.whl

Download URL symq-0.2.0-py3-none-any.whl
Size 513.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e0815581c8e6a5270769c42f0ca466dc6c6721eead4e07ba2c3999026f732b5f
BLAKE2b-256 checksum
How to use checksums
f30f0c3235743a7a3329ec767de5f52109a15cf4f870cdb11e3fd7ead468cddc
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL symq-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 546.5 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
afaac630e4fb4205edf42399e1e60395e043a36e841d0275b89efca361b01d1e
BLAKE2b-256 checksum
How to use checksums
0f02542ec02f3e60af31719abeba39498f330ed2661f5d280d68956edac981bc
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL symq-0.2.0-cp314-cp314-musllinux_1_2_aarch64.whl
Size 547.4 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
ddb8ef0d9979494f38836d437579ec429e38ad2d52200cc3672356545eaa120d
BLAKE2b-256 checksum
How to use checksums
03e5652a950ec08cd94ab6625d4535bf133a81474cba33826439e6d15800c075
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.9 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
a4c5e6d8095ead152dbc7391b4923ba39a8a5d3ccc6bd7f4d0b75107c3225c8b
BLAKE2b-256 checksum
How to use checksums
35f8ae742d46315ba43d7ad6d90a4e28460fa5414af2de2e26b960b6927ea532
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 547.1 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d56403e6e0143889348561725c05ff595d092d6bed7cdc773f23617bdb1bb4cd
BLAKE2b-256 checksum
How to use checksums
3e6cb0f51a74986763aa66cc3b32805b966e6ea75b054e679c99bfaa9fcd3e8e
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL symq-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
Size 538.9 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
78d9b3b89c9a6f016df50bb4093c514eb3fed61f9e9ae968f822e16b04cd9e88
BLAKE2b-256 checksum
How to use checksums
05b2d8791050aa6c0b0e93b716bc799d263895710d5933a9de3abe35d54c49ca
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl

Download URL symq-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl
Size 539.9 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
9563366b86954bfcd48e01cb91c20182993366b6e629de28fc28a33960238493
BLAKE2b-256 checksum
How to use checksums
b2363e46cb90ed11a0c8f7221c071bfed5533f79ec9c46d34797a086dff2b818
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL symq-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 546.6 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
e4271b0dbdea038b2ab3d02129c2f3554ec286c3584eb12d087a12cbae783279
BLAKE2b-256 checksum
How to use checksums
df32bef9d265feeffb62bb7998e5b2993ea2d4cc482586e35e646357615d7f06
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL symq-0.2.0-cp313-cp313-musllinux_1_2_aarch64.whl
Size 547.3 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
44b173929e7bb281a342995e8c9f278c2034f8638ac0b58256b44f12e8af8483
BLAKE2b-256 checksum
How to use checksums
aa028d1c9e2c90797fcea0b391ced431449d42c9748d7c33372602311ede5bc8
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.9 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
0635a28c5b1af6311977ffe89990747747e111bb4c7ec4c52b5f5d440a03481c
BLAKE2b-256 checksum
How to use checksums
e66f450547e10ed28633ed1d7c3cf3425c9d418739ba5624692d894cdda52614
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 547.0 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
e95c356fd7d28e548c0ae8678458ea0a95394b8e04a2e4016969990002f6ddc5
BLAKE2b-256 checksum
How to use checksums
9f117fdd1afd5645138ed2a99f3a1afcf823c14f1ec6faf439f9fda178c19b52
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL symq-0.2.0-cp313-cp313-macosx_11_0_arm64.whl
Size 538.9 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7e0e72e167079b7c47af556bafebd63b29dd5b5ddaf71cf7ecdd1b0a67acd2f8
BLAKE2b-256 checksum
How to use checksums
6d7447d9b2c49276ac5415c5dce2da4c311ddc09825c88c909cddd610b69e574
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl

Download URL symq-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
Size 539.8 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
c81010345837b8b9fd856ec342b961c6a03b49238f88a75bd03775fb98a70a35
BLAKE2b-256 checksum
How to use checksums
6c23613ee1eddd95473060f95c6524832edf88176c04779bd83448b12de76543
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL symq-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 546.4 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
ff56ad8c728d414c1e6b3176e27fde93e5b435739f6ec51adb6e3604782b650a
BLAKE2b-256 checksum
How to use checksums
a4561c1d62ab52829c96e22d76f88cd9e195e8bf069ff728e5516bddc9e25fa0
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL symq-0.2.0-cp312-cp312-musllinux_1_2_aarch64.whl
Size 547.1 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
60d866edabb2057b78d36c06fa129223b485449a4fe76fe90846070b65042fc4
BLAKE2b-256 checksum
How to use checksums
cbbb87836c5ef8fd4678c28590b553a9191b7e7e2712d95985b2831e0abf6ea5
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.7 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e9b31eb85db2da6a0a0a5bdb64a52427ebccadfd19ff1e3d59d9066322b0952d
BLAKE2b-256 checksum
How to use checksums
cec3685e1ffc2c4c49ef1735b80d1b3f323ab5db7f33a3cab5d31eb2769d075e
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 546.8 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
635b6bf747da12c7166b118bcb51a79d48cda8de91364fb4580f17a4dcab5ba4
BLAKE2b-256 checksum
How to use checksums
73d1b5c95c99a380c6872e0caa4c10ff9487d3be6a44077f04742057d0ff5037
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL symq-0.2.0-cp312-cp312-macosx_11_0_arm64.whl
Size 538.9 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
713f2218f403d938aad205ffa102b5d2e8bd187dde8577cd6c1dfbf9408a90f0
BLAKE2b-256 checksum
How to use checksums
2d7b21a9c502b7d238b0553a0e22ac20638a8fb9e6832b294e1b10713a74712c
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl

Download URL symq-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
Size 539.8 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
36e16808707d06e5a5e49411e7cf73f87fa3da24ba1afce4bc6c8108be48d290
BLAKE2b-256 checksum
How to use checksums
bef82848abb548bc3395b9cc1b1180a77e3b872305a062c22c6878ffe6fe551d
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL symq-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 545.6 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
db2065e50a6ccae3affe6390969770a439aba518efd52d5862d4f510a36ca008
BLAKE2b-256 checksum
How to use checksums
14214f45de13497486b8b87e91874f163919c3e016b31867b45bb52b09ebc6d8
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL symq-0.2.0-cp311-cp311-musllinux_1_2_aarch64.whl
Size 546.3 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
af1ab7e825dd345db0a818c06ec15de66df2b264e71195d159c613b03c5a19b4
BLAKE2b-256 checksum
How to use checksums
8c071feb7057daced9b6bb97efa57f24270728857636a5f8d4f3de25992e05da
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 544.9 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
15f3b5878a34f78d1ac460f80910f1b2b214cc601651356d4ff4a0f5f5cc34da
BLAKE2b-256 checksum
How to use checksums
088941c53b460400b1a7e3ad977fa7af150178d3e3e457cd1d8d588849e43efc
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 546.0 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
660ce5a7af572f6fb0638e576ce21be63c3933730bb63cd5660eb0382f12e9c3
BLAKE2b-256 checksum
How to use checksums
ef71aa983e91f85ae4a1f2176120d039d1e4f8987375ebdde599041313ac1120
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL symq-0.2.0-cp311-cp311-macosx_11_0_arm64.whl
Size 538.0 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
416d3fcb5db3ffa3e4151fa9ad007b77b69944e775ffdf4c5798ca51be88d04c
BLAKE2b-256 checksum
How to use checksums
b3899d15d9afb68e28133b87ae2c31bffef01c3b6f2db4f9f70fed00d6e336f9
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl

Download URL symq-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 538.5 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
902b65fb10b0ce8ca379cee5ff324d6fcb7b0caf5f502a6e99d572a710e2d6ed
BLAKE2b-256 checksum
How to use checksums
cc9167c27bd791944e582ded18293fa4810552145d407c3bd0586d39d9d827da
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL symq-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl
Size 545.7 kB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
103852f4b627ebd0511bfb0dd793891117c394061c87a9061d593a194ab0cf72
BLAKE2b-256 checksum
How to use checksums
0f8caba6ea654a4c892252f888fa4d72f81ae0a5b315c68b9b89c617019b1d64
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL symq-0.2.0-cp310-cp310-musllinux_1_2_aarch64.whl
Size 546.4 kB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
7b2d438a9d5f5943ba8e5f2003be5cfdccb1ed49dcae54ddc5848a549bec72b1
BLAKE2b-256 checksum
How to use checksums
c885e00341c39e94dc6f323dc8628e43fb9bdb0fa4c1186228fcf9657f28bd33
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.0 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
a5014a8aa042f7f9173592c39f28c074505c1c7f8531fa04fd27e35c61bde66c
BLAKE2b-256 checksum
How to use checksums
afa9c042e063b2db5ee5bbbf107163afa6c0bcb3a7604b836b9bb6c9151a7dc2
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 546.0 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3317ad93f094365e2d91ab964857f157f73d59db271c9a6f2bd853cd313154f0
BLAKE2b-256 checksum
How to use checksums
a9e7369b4134cbd4c92effa55bb4b68d0312aaa16828bb4b57800766b9e43341
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL symq-0.2.0-cp310-cp310-macosx_11_0_arm64.whl
Size 538.2 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
e6c0d5be74d015f1d60ebaf374d4a5d3981fa62aebdc0546f45fa79c6ae49794
BLAKE2b-256 checksum
How to use checksums
1fab92dd5a42a508dd890ae6c51610e3ba62797e90810bbf8f702b3a9f4a6ced
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 Nov 12, 2026.

Transparency log

Release files / symq-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl

Download URL symq-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
Size 538.5 kB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
6910ce36c946436b74ab6925565feaf2c2db467b84d1ac46f098a256753297bc
BLAKE2b-256 checksum
How to use checksums
a407ded49e93769017a100835527a7121ef41201b9b42130ee4e48137f3ae3d0
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 Nov 12, 2026.

Transparency log

Security for symq 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 32 files in this release have been uploaded with provenance metadata.

Select from 32 files

Attestation for symq-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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