Skip to main content

reeval-python

Python authoring SDK for reeval. Write *.eval.py files, declare evals with the same options as TypeScript, and run them through reeval's language runner (loopback TCP, attempt protocol v2).

Import as reeval_python (from reeval_python import evaluate). The PyPI distribution is reeval-python (the name reeval is already taken on PyPI by another project).

With reeval installed, default discovery includes evals/**/*.eval.py. When your project has pyproject.toml or uv.lock and uv is on PATH, reeval starts the runner with uv run --project <root> python -m reeval_python. Otherwise it uses <root>/.venv/bin/python when present, then python3. Set REEVAL_PYTHON to override the interpreter.

Install

uv add reeval-python
# or: pip install reeval-python

Monorepo development:

cd packages/reeval-python
uv sync --dev
uv run pytest
uv run ruff check .
uv run pyright

Declare trees are checked against packages/reeval/test/conformance/declare/ goldens. From the reeval package, test/python-sdk.test.ts runs the same suite in CI.

Writing evals

from reeval_python import evaluate, expect


@evaluate("lands")
def lands(c):
    c.send("Create greet.py that prints hi")
    assert c.exec("test -f greet.py").ok
    expect(c.judge("Does greet.py print hi?")).to_pass()

Plain assert is first-class: failures become hard checks in the run record (same shape as TypeScript). Use typed results (ExecResult.ok, Verdict.passed, Turn.text, …) and c.file(path) for quick checks. Keep expect for reeval matchers (to_have_file, to_succeed, soft checks, labels) — Playwright-style.

Use snake_case on the context (read_file, write_file, file) and on matchers (to_succeed, to_pass, to_equal, to_contain, …). Matcher failures raise ReevalAssertionError. Async bodies use async def, await c.send(...), and await expect(await c.exec(...)).to_succeed(); sync bodies use plain def and block on the runner loop.

Examples

  • Feature smoke: packages/reeval/test/features/python-sdk/hello/ (uv project with a project dependency)
  • Plan case: packages/reeval/test/plan/python/
  • Contributor guide: .agents/skills/add-a-language/SKILL.md in the reeval repo

Metadata

Release files for reeval-python 0.10.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 reeval-python 0.10.0
File Size Uploaded Provenance Actions
reeval_python-0.10.0.tar.gz 21.8 kB With provenance Details for reeval_python-0.10.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for reeval-python 0.10.0
File Interpreter ABI Platform Actions
reeval_python-0.10.0-py3-none-any.whl Python 3 none any Details for reeval_python-0.10.0-py3-none-any.whl

Total release size: 40.0 kB

Release files / reeval_python-0.10.0.tar.gz

Download URL reeval_python-0.10.0.tar.gz
Size 21.8 kB
Tags Source
SHA-256 checksum
How to use checksums
a7a25c994f2f1b73e2bb8f50bb5e92d78c180bcc2a88a24178fc49e2c8516033
BLAKE2b-256 checksum
How to use checksums
49bb6e7eafb509d0bb2bd2a82ec03bbdc4d1ff42bf00add0e56e0fb5c9c46036
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / reeval_python-0.10.0-py3-none-any.whl

Download URL reeval_python-0.10.0-py3-none-any.whl
Size 18.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
658b2f7a20fb4a43523a4c267128225a4c0bca8298bb4a00b32fa12a7d0214f2
BLAKE2b-256 checksum
How to use checksums
993314c0829ec6bc916277c988d077833ef69a647df6a3ee2982471403a02893
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Security for reeval-python 0.10.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 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for reeval_python-0.10.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 Oct 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.

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