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.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 symq 0.2.1
File Size Uploaded Provenance Actions
symq-0.2.1.tar.gz 1.6 MB With provenance Details for symq-0.2.1.tar.gz

Built distributions (wheels)

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

Total release size: 18.4 MB

Release files / symq-0.2.1.tar.gz

Download URL symq-0.2.1.tar.gz
Size 1.6 MB
Tags Source
SHA-256 checksum
How to use checksums
6a32593430238a979afbc0c2edfbc79c1f209fa27ba960b0481ec8f61fa9e0ce
BLAKE2b-256 checksum
How to use checksums
f6b022527e6c8e3d747ddc54669b758e6a19bdbfbd19df2183d2414a189111e4
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.1-py3-none-any.whl

Download URL symq-0.2.1-py3-none-any.whl
Size 514.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5eaef6c76df74a2d16649300b7f2d04d9b576be5c9514152d9a0c6f51a75736e
BLAKE2b-256 checksum
How to use checksums
ee4c8b5ee25b62a9796743d0a06709c26bea0b9226bbc2c9fcbe9a4f4f4bd8ef
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.1-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL symq-0.2.1-cp314-cp314-musllinux_1_2_x86_64.whl
Size 547.3 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
7009173a25064096b163abc8a9e24f15233d910c3b5ff11da0840794aa157f3a
BLAKE2b-256 checksum
How to use checksums
504a0920b428544d9bb78cae5cfdb165cdef926cd926b4038b5ae2c668af0bc2
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.1-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL symq-0.2.1-cp314-cp314-musllinux_1_2_aarch64.whl
Size 548.2 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
541406a02af95e207d868c13778d814b558a808c2999d0602faf27eb56441aa8
BLAKE2b-256 checksum
How to use checksums
beb2eaf4bb776f988bd291ead4f0f12f2458bc05faf8ec72b94b4337f4f21537
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.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 546.7 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
46e4d387aa39fc6ef6a8638b7f9c37a79a06558106ed3275a667d3cb3c5d5d77
BLAKE2b-256 checksum
How to use checksums
e9e29dd3abcdeb6412b59b20fcacf8b4beb917f7787928e3c460a116839a85d9
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.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 547.9 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
67503cc8ac957c23b24a7a061e410d709ad32b99aa0db64d55903b360638b419
BLAKE2b-256 checksum
How to use checksums
51816c05b2e56d7379dde5b91fb7027c19858a49450efe3850b1ce40fd587c32
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.1-cp314-cp314-macosx_11_0_arm64.whl

Download URL symq-0.2.1-cp314-cp314-macosx_11_0_arm64.whl
Size 539.7 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
1fe19881a0e1fddccd27795e7142994e39ac029b25a080c173035abbfd6ef964
BLAKE2b-256 checksum
How to use checksums
24ac95d3de19d252a2464aa0179983699c283edaa433b916bd6818816457c8d8
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.1-cp314-cp314-macosx_10_15_x86_64.whl

Download URL symq-0.2.1-cp314-cp314-macosx_10_15_x86_64.whl
Size 540.7 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
0b81827beaee23dfe6161a09fd0a3f341d605616d1f132007e8bd6eaecb2a4a9
BLAKE2b-256 checksum
How to use checksums
d20f6b207b254ca834d349263db393499d4210232bdc489ada30760d91a76439
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.1-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL symq-0.2.1-cp313-cp313-musllinux_1_2_x86_64.whl
Size 547.4 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
e55ebebefb44c5a677084fbe3ce450b8be41e2d38943611ed0408c171c1050fa
BLAKE2b-256 checksum
How to use checksums
dc79ce4b5315a6aa0662193d4cfe2177c461fdef9dd87706c3cb9c3de6e4618e
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.1-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL symq-0.2.1-cp313-cp313-musllinux_1_2_aarch64.whl
Size 548.1 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
cc492b6aebae466e40643f2ce25e92dbd5ed58e4f91e0be5154ccd4d9816b97d
BLAKE2b-256 checksum
How to use checksums
50475815392a16f96d4b122e83d3a27b862115d95d41da846f8146453fe1ef28
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.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 546.8 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
465dc44700a2b8389b2f06598063dc9e3e4243f5f0f915e8be3a69985e7fb9e7
BLAKE2b-256 checksum
How to use checksums
7e436e637e23fdc95294db8e37aa3c239f4ecc736afb8e0153588005ee2c4f48
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.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 547.8 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f3f75f7fe9a1492a15fcca42b5086933ad3872dd0cb2b412e2cd23a3af4ba205
BLAKE2b-256 checksum
How to use checksums
1a9066c6eae5ae7fcd5c94d534b98baaf183df90081d4fce58c653a96c6d0d14
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.1-cp313-cp313-macosx_11_0_arm64.whl

Download URL symq-0.2.1-cp313-cp313-macosx_11_0_arm64.whl
Size 539.7 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d50bdb19a6f11ae8b4b884c70b9c4f4a9d6101d3892b551e58b23619e8e92781
BLAKE2b-256 checksum
How to use checksums
e07628ec2727b778b1f38d8c99d041599fa4a0c1dadeed22e855a20ecfbd83d2
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.1-cp313-cp313-macosx_10_13_x86_64.whl

Download URL symq-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl
Size 540.7 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
36dfdec18899d6ec6453df7dda5d079a238d4bf7718bd85c476fc1ce70d086e3
BLAKE2b-256 checksum
How to use checksums
047dd71a1d8259b5799315e873e45f4be084f4f1881b29540450f84ee2aa1197
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.1-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL symq-0.2.1-cp312-cp312-musllinux_1_2_x86_64.whl
Size 547.2 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
e84dbb5a491f104fd3c35692a386ce0adfc5d7ba19951bba5e81e1141516584c
BLAKE2b-256 checksum
How to use checksums
1ce48b6a3fa937d6a748d3d9b25d1381834757df7ffdecd6ea814834c26bb6dc
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.1-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL symq-0.2.1-cp312-cp312-musllinux_1_2_aarch64.whl
Size 548.0 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
498c67326aa4abad0808030d3a5e6b7d25f487acc330587e54415ea84a03262e
BLAKE2b-256 checksum
How to use checksums
08ff56fecdd7733ba8332454dc2ddc13e8cd05e4f33d5d9e64430870f9064de1
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.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 546.5 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
08dc9b1db7cfd5fdd388226ba5028f15b4c8106aee80174b623459cccd0106cb
BLAKE2b-256 checksum
How to use checksums
d8b860e3e39dd00bb8e9b4fb4e296b3b2fdb4faaff3fc7fd3fed18f27d43bb9f
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.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 547.7 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
8bf12e8db6d4bf60bc1c734efe7f3db46bd54967516242af456183141e113ae3
BLAKE2b-256 checksum
How to use checksums
4714568e70411775969a620b8e0fd03250ded7b6ff8ef6b2a66e3ddfa8021c20
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.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL symq-0.2.1-cp312-cp312-macosx_11_0_arm64.whl
Size 539.7 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
0ad3ac30d76c9e0727fb2586f0c5908a197c86af550596dd6dd6dbe9af50fd82
BLAKE2b-256 checksum
How to use checksums
f528666789cf89eebe2ac8c62b985bbf39fdf4e6215585f22dda7aed6a88538a
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.1-cp312-cp312-macosx_10_13_x86_64.whl

Download URL symq-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl
Size 540.6 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
90d79a7d6b6c2c0ec427a1ff1770717126334cbf01250c7754684e75abf743d8
BLAKE2b-256 checksum
How to use checksums
3379fbbb96031311fd14a1bbe1aefdfd0e9bd8ab3213de6240e5836b52951bfc
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.1-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL symq-0.2.1-cp311-cp311-musllinux_1_2_x86_64.whl
Size 546.4 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
e6e38f4cea452c267abd2a1789a21cb24b49e57644fce28496327fe6502bcb31
BLAKE2b-256 checksum
How to use checksums
27a3028ce421f60706ed3002a67cb296e133466ab25cfa4048016f0c7f7497da
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.1-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL symq-0.2.1-cp311-cp311-musllinux_1_2_aarch64.whl
Size 547.2 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
c61cfcbba90e2d7dbca2fa081a041cb10f9dc84f22a5c5e73d4b6b1f10bab231
BLAKE2b-256 checksum
How to use checksums
04a2c501ba65d3c09986361140f874d2fb9aeffe0f0af507f6186e3645b816c4
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.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.7 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
68db3993cb6750c342a02b8c0ba1a124428e6156677564ec1c7dcec7bec236ae
BLAKE2b-256 checksum
How to use checksums
2e9e3156001b6223ce14739835e19c4c8c23f54e4980d52437aeb435c12aa09d
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.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 546.8 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
13f4d7ea427e824950c395143d33632f5dc6a72af206a56191e205b1e1abb001
BLAKE2b-256 checksum
How to use checksums
263c0e537c8e2a161d9287a9f58a2f7785e25bc16e66aebb28f5d4a1d2c6a560
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.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL symq-0.2.1-cp311-cp311-macosx_11_0_arm64.whl
Size 538.9 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ee363bb2eb67b88594aaa90ca0074dceb36fda263b937dcd6df01ae9937f3e22
BLAKE2b-256 checksum
How to use checksums
b65523d579788ade6ef0c0f4e3826f25ebd9d5b38563993de16ab319c3e19ad1
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.1-cp311-cp311-macosx_10_9_x86_64.whl

Download URL symq-0.2.1-cp311-cp311-macosx_10_9_x86_64.whl
Size 539.3 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
31b1593dfbde36912a21e925fef5f88adf267644eae364b68e9b847934d82459
BLAKE2b-256 checksum
How to use checksums
5e859dac34ddedeb3f8e5037342fd08d2c7b8e2f440ca2ae7a8ad4b9a9641e1f
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.1-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL symq-0.2.1-cp310-cp310-musllinux_1_2_x86_64.whl
Size 546.5 kB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
c9242d1ba3dc2bc6bdeaf058965881e891ea6a25519ad3261a1cc3c2023c3290
BLAKE2b-256 checksum
How to use checksums
e0ffaf26ecd641f2ce9fc7fed57bd60aabbf319b15b1e64bba8e64177f5aa07e
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.1-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL symq-0.2.1-cp310-cp310-musllinux_1_2_aarch64.whl
Size 547.2 kB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
c7f4f89c12ad84981a3dff3443bd5a273d0195d02d3954c056822d66e94a2865
BLAKE2b-256 checksum
How to use checksums
701d75fe443c7a288d678919814a67751792c00d045ba1bddc4f2948d66ecdd7
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.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 545.9 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2bb5e6bd20e8449e35cca06ad183f194305ed5344367a160ddbb2f1fbbf3b96d
BLAKE2b-256 checksum
How to use checksums
ddedfe177176ab46742f6ec6a20b5fb82989ef4c8c0931b3588d11d491fed5a5
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.1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.2.1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 546.9 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
bd256a82ad4a8c12587c85e7bccc64ebf6df093851a08ccf6ebf658e67b7adbf
BLAKE2b-256 checksum
How to use checksums
c95f59fdffc2ecbf3c535d85b9bc6222935eae1172efd693160aa9664dde1a9d
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.1-cp310-cp310-macosx_11_0_arm64.whl

Download URL symq-0.2.1-cp310-cp310-macosx_11_0_arm64.whl
Size 539.0 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
122ba92f0f514e24b29c0456d50b35af4d34cf71a018f058539e85de6c35f2b5
BLAKE2b-256 checksum
How to use checksums
0f0399a199eae00e12c10f5264f8a56b0ea947e9a671d018a041475b71aad424
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.1-cp310-cp310-macosx_10_9_x86_64.whl

Download URL symq-0.2.1-cp310-cp310-macosx_10_9_x86_64.whl
Size 539.3 kB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
0f12203d85844a8f5f73343cea194a0e8fa6d24f14cc3e7ddf3c0dbcc76324e4
BLAKE2b-256 checksum
How to use checksums
d4f708ee71c3b7a83f144a31f0f00e4d63ba8b968f174677941547eb07b2b8ea
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.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 32 files in this release have been uploaded with provenance metadata.

Select from 32 files

Attestation for symq-0.2.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 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