Skip to main content

⚡ Turing Engine

A small, readable LLM inference server for testing KV-cache and quantization ideas against real models, where every number in the docs comes from a committed results file.

Docs: Live Release: v2.0.0 License: BSL 1.1 Tests: 1108

Open In Colab


Is it faster than vLLM or llama.cpp?

Mostly no; in a few measured settings, yes. On one NVIDIA L4, same model and prompts (Qwen2.5-1.5B-Instruct, 512-token prompts, 256 new tokens; results_4bit_speed_cuda.json, results_4bit_quality_*_cuda.json):

Setting Batch 1, tok/s Batch 8, tok/s Batch 64, tok/s GSM8K (n=500)
llama.cpp Q4_K_M 180 752 2,157 52.4% ± 2.2%
vLLM GPTQ-Int4 (Qwen's checkpoint) 171 1,093 3,065 50.2% ± 2.2%
Turing GPTQ 155 1,035 2,739 50.4% ± 2.2%
Turing GPTQ + 4-bit LM head (opt-in) 197 1,266 2,961 51.8% ± 2.2%
Turing GPTQ + TEAL 25% 107 953 2,600 46.2% ± 2.2%
Turing GPTQ + TEAL 40% 112 960 2,614 42.0% ± 2.2%
vLLM fp16 (reference) 75 537 2,235 —
Turing fp16 (reference) 73 530 2,152 —
  • fp16: vLLM is 1.01–1.04× faster at batch 1–64. On SmolLM2 at 1,024-token prompts Turing reaches 88–103% of vLLM's throughput, and its first token at batch 64 on SmolLM2-1.7B takes 2.3× as long (6.7 s against 2.9 s).
  • 4 bits, fp16 LM head (default): vLLM is 1.06–1.12× faster. llama.cpp is 1.17× faster at batch 1; Turing is faster than llama.cpp at batch 8 and 64 (1.38× and 1.27×).
  • 4 bits with the opt-in 4-bit LM head (--quantize-lm-head): Turing is 1.15–1.16× vLLM at batch 1 and 8 and 1.09× llama.cpp at batch 1; vLLM stays 1.04× faster at batch 64. This quantizes one more matrix than vLLM's GPTQ checkpoint does; GSM8K 51.8% against vLLM's 50.2% (each ± 2.2%).
  • 16K-token prompts, fp16 KV at equal memory: Turing is 1.0–1.22× faster per request than vLLM, more at larger batches. vLLM's fp8 cache with layer 0 kept in fp16 (the setting that is correct on this model) is 1.3–1.4× faster than Turing's int8 at equal quality.
  • Cold start: from process start to first token Turing takes 25.4 s from a cold page cache and 10.0 s warm, against vLLM's 51.7 s and 34.2 s. vLLM was measured in an earlier session, where Turing's code at the time took 27.4 s and 12.1 s (1.9–2.8× sooner); llama.cpp with its 4-bit GGUF takes 7.1 s and 1.3 s (results_cold_start_*_cuda.json).

Details and every other setting are in the comparison. For production serving use vLLM, SGLang or TensorRT-LLM; on a laptop, llama.cpp or Ollama.

What it is good for

  • Low-bit KV caches that do not silently break the model. When a pool stores KV in int8 or int4, Turing measures at startup which layers that format damages (each layer's K and V are round-tripped alone and the change in the next-token distribution is measured on random tokens, in a few seconds) and keeps those layers in the model's dtype; outlier key channels are scaled down for int4. On Qwen2.5-1.5B-Instruct vLLM's default fp8, per-token fp8 and per-token int4 caches collapse (GSM8K 0.6–2.4%); Turing's int8 and int4 keep it working with no setting:
KV cache Layers kept in bf16 GSM8K Pass-key 2K–32K ΔNLL vs bf16 s/request (16K, B=128)
Turing bf16 (reference) — 57.2% 100.0% — 2.05
Turing int8 — 58.2% 100.0% +0.003 ± 0.002 2.32
Turing int4 automatic 52.8% 100.0% +0.020 ± 0.005 2.95
vLLM bf16 (reference) — 57.4% 100.0% — 2.51
vLLM fp8 — 2.4% 5.0% +2.286 ± 0.394 1.66
vLLM fp8 layer 0 (manual) 56.8% 100.0% +0.013 ± 0.003 1.73
vLLM fp8_per_token_head — 0.6% 0.0% +2.404 ± 0.364 —
vLLM int8_per_token_head — 41.4% 100.0% +0.023 ± 0.007 4.72
vLLM int4_per_token_head — 0.6% 0.0% +8.127 ± 0.495 4.41
vLLM int4_per_token_head layer 0 (manual) 47.8% 100.0% +0.058 ± 0.010 4.30
vLLM turboquant_k8v4 — 52.0% 100.0% +0.001 ± 0.001 —

vLLM fp8 with layer 0 skipped by hand matches Turing's quality at 0.6–0.75× Turing's time per request, which is the point: the calibration finds that layer automatically. It is also packaged on its own for vLLM users, under Apache-2.0: packages/kv-layer-guard. Validated on six instruct models (Qwen2.5 1.5B and 7B, Llama 3.2, Gemma 2, Phi-3.5, Mistral), including one limit it does not catch (benchmarks §2).

  • Measured correctness. The exact model reproduces HuggingFace's logits on 16 model families in the tests, 13 of them also on real checkpoints (models & hardware); 13 real GGUF files agree with llama.cpp.
  • A codebase small enough to change. Paged KV pool, Triton decode kernels, GPTQ, TEAL sparsity, prefix caching, speculative decoding and the OpenAI, Anthropic and Ollama APIs are a few Python modules and kernels, with a standalone C++ engine beside them. The eval scripts (scripts/eval_kv_quality.py, turing eval-accuracy, turing eval-niah, the Turing-vs-vLLM and llama.cpp benchmarks) run any idea against real models.

Not measured: multi-GPU (tensor and pipeline parallelism are tested as CPU processes only), models larger than Qwen2.5-7B (7.6B), SGLang and TensorRT-LLM.


Quickstart

1. Install from source

git clone https://github.com/intutic/turing.git && cd turing
pip install -e .                     # builds the C++ extension
pip install -e ".[structured]"       # optional: JSON-schema and tool_choice enforcement (llguidance)

The package is not on PyPI yet; the release workflow (.github/workflows/release.yml) publishes wheels and Docker images when a version tag is pushed. Docker: docs/docker.md.

2. Chat in the terminal

turing chat --model smollm2                                   # alias for HuggingFaceTB/SmolLM2-135M
turing chat --model Qwen/Qwen2.5-0.5B-Instruct
turing chat --model ./models/qwen2.5-0.5b-instruct-q8_0.gguf  # llama.cpp GGUF, no conversion

3. Serve OpenAI, Anthropic and Ollama APIs on one port

turing serve --model Qwen/Qwen2.5-7B-Instruct --port 8000

OpenAI (/v1/chat/completions, /v1/completions, /v1/embeddings), Anthropic (/v1/messages) and Ollama (/api/chat, /api/generate, /api/pull, …) clients can point at http://localhost:8000. The server listens on 0.0.0.0 by default and needs no key unless started with --api-key (or TURING_API_KEY).

4. Quantize to 4-bit once, serve the result

turing convert --model Qwen/Qwen2.5-7B-Instruct --output ./qwen7b-gptq --method gptq
turing serve --model ./qwen7b-gptq

5. Turing DSL

import turing

@turing.chain(model="smollm2", device="auto")
def three_answers(question: str):
    turing.gen(f"Question: {question}\nThink step by step.", max_tokens=64)
    branches = turing.fork(3, temperature=0.8)   # the context so far is prefilled once and shared
    for i, b in enumerate(branches):
        b.gen(f"\nAnswer {i + 1}:", max_tokens=64)
    return turing.join(branches, strategy="best")  # highest mean log-probability

6. Standalone C++ engine (turing-cli)

cmake -B build && cmake --build build
./build/turing-cli generate --model ./models/llama-3.2-1b-instruct-f16.gguf --prompt "Hello"
./build/turing-cli serve --model ./models/llama-3.2-1b-instruct-f16.gguf --port 8000   # binds 127.0.0.1

It runs Llama-layout GGUF models (RMSNorm, SwiGLU, RoPE, grouped-query attention) on the CPU with AVX2 or NEON, with an optional int8 KV cache (--kv-cache-dtype int8).

7. Tensor and pipeline parallelism

./scripts/launch_distributed.sh Qwen/Qwen2.5-7B-Instruct 2 2   # MODEL TP PP, via torchrun; rank 0 serves HTTP

Sharded weights and KV pages over torch.distributed. The tests run TP 2/4, PP 2 and TP 2 × PP 2 as CPU (gloo) processes and compare logits with a single process; no multi-GPU (NCCL) run has been recorded.


Models

tests/test_hf_parity.py checks prefill, chunked prefill, decode and batched decode against HuggingFace (atol 1e-3) for 25 configurations of these model types: llama, mistral (sliding window), qwen2, qwen3, gemma, gemma2 (soft-capping), gemma3_text (local/global RoPE), phi (Phi-2), phi3 (incl. LongRoPE), gpt2, opt (incl. post-LN and projected embeddings), gpt_neox, mixtral, qwen2_moe, qwen3_moe and olmoe. RoPE scaling types: default, linear, dynamic, YaRN, LongRoPE, Llama 3 and proportional. Any other architecture is refused before download (hf_loader.FAMILIES, ArchitectureRegistry); weights never fall back to random values. Every family except OPT also loads from GGUF (Mistral and Mixtral through llama.cpp's llama architecture). Details: models & hardware.

Hardware

Recorded runs exist for an NVIDIA L4 (CUDA, Triton kernels, CUDA graphs), an Apple M4 Pro (MPS) and CPUs. --device also accepts rocm (PyTorch's HIP build) and the auto-detection picks xpu or vulkan when PyTorch reports them, but none of those has been run.


Features

Area What the code does
KV cache One paged pool per model (16-token pages), native/int8/int4 storage with the layers that format damages kept in the model dtype (chosen at startup), copy-on-write forks; Quest page selection (--kv-page-budget), also inside CUDA graphs
Prefix caching Automatic: full pages indexed by chained token hashes, reused copy-on-write, evicted LRU (--no-prefix-caching)
Speculative decoding Prompt lookup (no draft model), --draft-tokens (default 4); output distribution equals plain decoding for greedy and sampling
Weights fp32/fp16/bf16; 4-bit GPTQ or RTN (turing convert, --quantization); TEAL-style activation sparsity in batch-1 decode on CUDA (--activation-sparsity, off by default)
LoRA Several PEFT adapters at once (--lora NAME=PATH), chosen per request by model: "base:NAME" or X-Turing-Adapter
API Chat templates, tools (OpenAI and Anthropic; Hermes, Mistral and Llama 3 call formats), reasoning (reasoning_content, Anthropic thinking blocks, effort budgets), JSON schema by token-level constrained decoding, stop strings, usage with cached tokens
Traffic Admission control sized to the KV pool and three QoS lanes, on by default (429/503 with Retry-After)
Other endpoints Embeddings, rerank, /v1/extract, render endpoints, Prometheus /metrics, llm-d KV events
Distributed Tensor and pipeline parallelism (torchrun); prefill/decode disaggregation over TCP (--prefill-worker, --prefill-server)
Evals turing eval-accuracy (GSM8K exact match) and turing eval-niah (pass-key retrieval), through the engine on real weights

The repository also holds research components outside the serving path: cross-model KV transfer, clean_base lineage, k-slot pooling, an MoE expert-offload runner, hybrid linear/softmax attention (needs a model trained with it) and untrained Matryoshka draft heads. What was measured on real models, including what did not work, is in research findings.


CLI

turing serve --model <id|.gguf|.tgate4 dir> [--port 8000]   # HTTP server
turing chat --model <id>                                    # terminal chat
turing generate --model gpt2 --prompt "Artificial intelligence is"
turing convert --model <hf id> --output <dir> [--method gptq|rtn]
turing eval-accuracy --model <id> --samples 100             # GSM8K, k-shot greedy
turing eval-niah --model <id> --context-len 1024 4096       # pass-key retrieval
turing info                                                 # devices and runtime

Client SDKs

from openai import OpenAI
client = OpenAI(base_url="http://localhost:8000/v1", api_key="unused")
r = client.chat.completions.create(model="Qwen/Qwen2.5-7B-Instruct",
                                   messages=[{"role": "user", "content": "Write a binary search in Python."}])
print(r.choices[0].message.content)

import anthropic
client = anthropic.Anthropic(base_url="http://localhost:8000", api_key="unused")
m = client.messages.create(model="Qwen/Qwen2.5-7B-Instruct", max_tokens=128,
                           messages=[{"role": "user", "content": "Hello"}])
print(m.content[0].text)

import ollama
client = ollama.Client(host="http://localhost:8000")
print(client.chat(model="Qwen/Qwen2.5-7B-Instruct", messages=[{"role": "user", "content": "Hello"}])["message"]["content"])

Documentation


📄 License

Turing Engine is licensed under the Business Source License 1.1 (BSL 1.1).

  • Free for non-production use: development, local testing, academic research, personal single-GPU workstations and benchmarking (LICENSE, Additional Use Grant). Production use (multi-GPU clusters, commercial hosting, revenue-generating API traffic) needs a separate commercial license.
  • packages/kv-layer-guard/ (the KV layer calibration, usable with vLLM) is under the Apache License 2.0 now.
  • Converts automatically to Apache 2.0 on August 24, 2030 or the fourth anniversary of the first public release (as LICENSE §3 states).

Metadata

Release files for turing-engine 2.0.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 turing-engine 2.0.0
File Size Uploaded Provenance Actions
turing_engine-2.0.0.tar.gz 553.1 kB With provenance Details for turing_engine-2.0.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for turing-engine 2.0.0
File Actions
turing_engine-2.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for turing_engine-2.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
turing_engine-2.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for turing_engine-2.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
turing_engine-2.0.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for turing_engine-2.0.0-cp312-cp312-macosx_11_0_arm64.whl
turing_engine-2.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for turing_engine-2.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
turing_engine-2.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.27+ ARM64, Linux glibc 2.28+ ARM64 Details for turing_engine-2.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
turing_engine-2.0.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for turing_engine-2.0.0-cp311-cp311-macosx_11_0_arm64.whl
turing_engine-2.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for turing_engine-2.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
turing_engine-2.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for turing_engine-2.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
turing_engine-2.0.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for turing_engine-2.0.0-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 6.9 MB

Release files / turing_engine-2.0.0.tar.gz

Download URL turing_engine-2.0.0.tar.gz
Size 553.1 kB
Tags Source
SHA-256 checksum
How to use checksums
ce25bc0d67a2f630b26238d6875554fc17e0398bb2350708374480049cc104a6
BLAKE2b-256 checksum
How to use checksums
fd1d4ec4487d5b9d24c9bbe098efbca5b6101307640c9de6246fa24ed6b44b13
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL turing_engine-2.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 758.5 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
382945fa2e1ea938922f117be0a4d57a579aa14f11ef83c96e4439a3d4513e7e
BLAKE2b-256 checksum
How to use checksums
ccb4052122989604689230da795ae123242a193669588c56a7cdf9fbab5a8893
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL turing_engine-2.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 700.9 kB
Tags CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
74421d1b4be055064eb4dbb507fd3f1eae8749c2cb1ac73ad370204e5d27cabc
BLAKE2b-256 checksum
How to use checksums
aaa84932354bb37a460e1d1243126f3c7bdc1b2debc99b0920b593973d423cd5
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL turing_engine-2.0.0-cp312-cp312-macosx_11_0_arm64.whl
Size 652.0 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a829e25c268c07960b775e89bebb2646772a3ba72ef54a4342c86a4cdecf41f0
BLAKE2b-256 checksum
How to use checksums
118a5ec4a7f284f1851cf8a8d6dcba6ba493b766ac81f1652037677956fe0242
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL turing_engine-2.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 752.7 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
23dfe5155ea560fa2e4f9d0d74b327b617ce6e79a1bc2d59c37d620d848a16b0
BLAKE2b-256 checksum
How to use checksums
c4356a278241f28699e547eb70aba1a94d6573d54d6dd259f95b5238f00ea0b5
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL turing_engine-2.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 698.0 kB
Tags CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
2c3687a9cb04317cb8d6e4ceeec74c62bbfaf5fb89be57d873558e7e88ee98de
BLAKE2b-256 checksum
How to use checksums
725b763230209e3dbb2105cdecc90f04656e8a36efac5b93e147777fc3fe1006
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL turing_engine-2.0.0-cp311-cp311-macosx_11_0_arm64.whl
Size 650.3 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
fd75102d55e3d72da233dce92a11e4fba27298b1d65c099eb1049fd8e60175f8
BLAKE2b-256 checksum
How to use checksums
b5537664b3b0c01858436a68fb0dcd405c19a136fc81a03de403fbc0d4f24edf
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL turing_engine-2.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 752.7 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e1bf1e2aee929fcf39cf4fda4fddd70c00b8d9e546dcafeef970f5dead2b85c3
BLAKE2b-256 checksum
How to use checksums
c6975ce75d2972073fbb9630e870070ab617fe7853d84323551f3451f0592aaf
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL turing_engine-2.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 697.4 kB
Tags CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
9cbc8194639094fc0908c561afbb8c6671398c0336762cbf3442df70a4bc20ce
BLAKE2b-256 checksum
How to use checksums
63c6fdbd0466fcca0fe9de9f54df473dc09a35903df48bc1dc189422853046ed
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 20, 2026.

Transparency log

Release files / turing_engine-2.0.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL turing_engine-2.0.0-cp310-cp310-macosx_11_0_arm64.whl
Size 649.3 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
fe174f4bfcbff27df5de3b948b6ded11adcb2f0972db2ba75e9f59cced84e52e
BLAKE2b-256 checksum
How to use checksums
7ec2d70c1e7fcfd03a4dcf238f99d861b6b22a0abb15503e7f9e10af70eeae13
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 20, 2026.

Transparency log

Security for turing-engine 2.0.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 10 files in this release have been uploaded with provenance metadata.

Select from 10 files

Attestation for turing_engine-2.0.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 20, 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.

Release history Release notifications | RSS feed

This release

2.0.0 This release

10 release files Full provenance

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