# pexpect — PyPI project page

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | async-pty-process-testing |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | pexpect |
| Source URL | https://pypi.org/project/pexpect |
| Source publisher / author | pexpect maintainers (PyPI) |
| Source type | repository |
| Source date (published) | Unknown — not stated |
| Date researched | 2026-10-09 |
| Researched by | tai (agent), model: Claude Sonnet 5, on behalf of retoor |
| Research method | web search synthesis |
| Confidence | Medium |
| Status | Active |

## Summary

pexpect is a well-established pure-Python library for spawning child applications, controlling them, and responding to expected patterns in their output. Its own documentation explicitly lists automated software testing as a use case. It is built on the stdlib `pty` module (Unix-only for its main features) and is a blocking/synchronous library.

## Key findings

- pexpect's documented purpose statement explicitly includes "automated software testing" alongside general automation.
- Its core features require the stdlib `pty` module, which limits full functionality to Unix-like systems (some features — waiting for patterns from file descriptors or subprocesses — are also available on Windows, per the project's own docs).
- It is blocking for async I/O (a third-party comparison table makes this claim, though the research flagged that table as coming from a competing library's vendor, i.e. a potentially biased source — still consistent with pexpect's own synchronous API design).

## Pros / strengths

- The most mature, widely-used library in this space, with a long track record specifically for testing interactive terminal programs.
- `expect()`-style pattern matching against output is exactly the turn-boundary-detection problem `tai_test.py` needed to solve for REPL-mode testing.

## Cons / limitations / caveats

- Synchronous/blocking — adopting it inside `tai_test.py` would have meant either running it in a thread executor on every call or accepting that it blocks the event loop, neither of which fit an asyncio-native framework cleanly.
- Not independently trialed in this research pass; findings are based on its documented feature list and use-case statement, not hands-on testing of its API against `tai.py`.

## Relevance to tai

Surveyed and explicitly not adopted. `tai_test.py`'s `ManagedProcess.wait_for_pattern()` is functionally pexpect's `expect()` reimplemented natively in asyncio (regex matching against an accumulating, ANSI-stripped buffer read from an `asyncio.StreamReader`), chosen specifically so the whole framework stays asyncio-native rather than mixing in a blocking dependency.

## Changelog

| Date | Change |
|---|---|
| 2026-10-09 | Initial dossier created. |