Skip to main content

partial-python

Execute append-only Python while source is still arriving. Python 3.11+, no runtime dependencies.

uv add partial-python

Input and completion

Use an Executor for each logical response. Feed source as it arrives, then explicitly finish or abort according to the provider's completion status.

from partial_python import Executor

executor = Executor({"foo": foo, "bar": bar, "baz": baz})
await executor.feed("await foo(1)\n")  # Executes now.
await executor.feed("await bar(2)")  # Waits: an operator or attribute access may follow.
await executor.feed("\nawait baz(3)")  # Executes bar, buffers baz.
await executor.finish()  # Successful EOF permits baz.

Units execute in source order, at most once each. New input never reruns earlier units. A loop still performs its ordinary iterations, but its whole body must be sealed before execution starts.

feed() accepts new text deltas, not accumulated snapshots. feed() and finish() return completed Execution events. The executor retains events, failed_unit, sealed but unstarted queued units, and an immutable parser_state snapshot containing the unsealed pending tail. Read results from executor.namespace.

finish() declares successful source completion. On disconnects, token limits, cancellation, or failed responses, use await executor.aclose() to abandon pending source and release open contexts. abort() is a synchronous alternative when no context is open; cancel and await an active operation first. Failure is terminal: earlier effects remain, later units do not start, and nothing is retried. Lifecycle and integration.

Streaming blocks

Executor and incremental_exec accept stream_blocks, defaulting to ALL. Block is a Flag; NONE, MODULE, IF, WITH, ASYNC_WITH, and ALL are its aliases, exported from both partial_python and partial_python.blocks.

from partial_python import ALL, ASYNC_WITH, MODULE, NONE, WITH, Executor

executor = Executor()  # ALL: stream all supported block kinds.
without_async_contexts = Executor(stream_blocks=ALL & ~ASYNC_WITH)
without_contexts = Executor(stream_blocks=ALL & ~(WITH | ASYNC_WITH))
top_level_only = Executor(stream_blocks=MODULE)
whole_module = Executor(stream_blocks=NONE)

The argument replaces the selection; it does not extend the default. Include MODULE to execute before EOF. Without it, even with another flag selected, the executor buffers the whole source and compiles it once at successful EOF. NONE is the explicit whole-module mode.

IF, WITH, and ASYNC_WITH allow executing stable statements inside those blocks before the enclosing block closes. Conditions and context headers execute once. ALL is exactly MODULE | IF | WITH | ASYNC_WITH; it does not opt into unsupported compound kinds. Loops, try, match, functions, and classes still require their complete statement.

A context can stay open while more source arrives. With ASYNC_WITH, an asyncio.timeout(...) includes time spent waiting for later source; locks and transactions can also span generation. Disable a flag with & ~ when that lifetime is unsuitable, or select MODULE to hold every compound until it closes. Operations spanning an open context must use the same caller task.

An early body effect does not emit an Execution event. Events still represent completed top-level units. A failed or abandoned block can therefore have effects without a completed event, and those effects are never replayed or rolled back.

Async text iterators

When your adapter already supplies a validated async text iterator, incremental_exec() is a convenience wrapper. validated_deltas must yield raw source and end normally only after successful generation. Its adapter must raise on truncation, failure, or a missing completion signal.

from partial_python import incremental_exec

namespace = await incremental_exec(validated_deltas, {"foo": foo, "bar": bar})

Execution starts while source is arriving; the await completes after execution and returns the namespace used. To consume events as each unit completes, use Executor.stream() and retain the executor for diagnostics. Close a partially consumed event iterator with aclosing in its owning task/context. Streaming adapter.

Stable boundaries

These are the boundaries exposed by Parser and by stream_blocks=MODULE. The default ALL permits earlier body effects in supported blocks without changing the completed top-level units.

Input Execution boundary
Top-level simple statement A real logical newline or successful EOF.
foo() at temporary EOF Wait; it can still become foo() + bar().
for, if, try, def, and other compounds Hold the entire statement until an unambiguous top-level successor or successful EOF.
else, elif, except, finally, or an ambiguous prefix such as e Keep clauses attached; wait for ambiguous prefixes to resolve.
Blank lines and comments Preserve them; they do not close a suite.
Decorators, brackets, line joins, and strings Keep their complete logical statement together.

Parser.feed() / finish() expose the same boundaries as immutable CodeUnit source slices without executing them. pending retains the uncommitted suffix. Every unit preserves original characters and source positions; no repaired text is executed. Precise semantic contract.

Display completion

from partial_python import Allow, complete

assert complete("ready = 1\nvalue = ['hel").source == "ready = 1\n"
preview = complete("value = ['hel", Allow.STRING | Allow.BRACKET)
assert preview.source == "value = ['hel']"
assert preview.provisional

The default returns only the stable prefix. Allow flags opt into provisional display; prefix, suffix, and withheld distinguish original text from synthetic text. A preview never authorizes execution, even when its suffix is empty. Preview options and limits.

Execution scope

Units share one namespace and support native top-level await. Execution requires an asyncio event loop; use the asyncio backend with AnyIO. Parser and complete are synchronous.

With MODULE enabled, execution uses sequential compilation units, with explicit differences from whole-module execution. Future imports remain in the prologue, only the initial string sets the module docstring, and module-scope global declarations are rejected. On Python 3.14+, module annotations require an explicit from __future__ import annotations. Choose NONE for native whole-module global and deferred-annotation semantics.

In-process execution provides no sandbox or rollback. Hosts own permissions, background tasks, source limits, and hard deadlines. The integration examples demonstrate transport completion, concurrent reception, and traceback source lifetime.

Development

uv sync
uv run pytest
uv run basedpyright
uv run ruff check .
uv run ruff format --check .
uv run examples/streaming_tools.py
uv build

API and transport · Design · Validation · Related implementations

Metadata

Release files for partial-python 0.1.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 partial-python 0.1.0
File Size Uploaded Provenance Actions
partial_python-0.1.0.tar.gz 26.0 kB Without provenance Details for partial_python-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for partial-python 0.1.0
File Interpreter ABI Platform Actions
partial_python-0.1.0-py3-none-any.whl Python 3 none any Details for partial_python-0.1.0-py3-none-any.whl

Total release size: 54.9 kB

Release files / partial_python-0.1.0.tar.gz

Download URL partial_python-0.1.0.tar.gz
Size 26.0 kB
Tags Source
SHA-256 checksum
How to use checksums
c4a9a936c292129ee194a7673fd8a3ceb6aa44b8a8ba00fa11241e47d155e2ca
BLAKE2b-256 checksum
How to use checksums
4117250cf344234988341f1f59b639e412ab1c392aa0b3497d2d0717f5c3c2ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / partial_python-0.1.0-py3-none-any.whl

Download URL partial_python-0.1.0-py3-none-any.whl
Size 29.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1de770a28d4b60036c6bc85414241c541d75169321119cfdd435a4aee77c425a
BLAKE2b-256 checksum
How to use checksums
5f06899feae13bd61562bcf5992c472bbb6d1f13ed73fa6f284ba8207b35d7bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for partial-python 0.1.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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