Skip to content

docs: full-suite verification for interpreter-compat changes #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lesnik512 merged 1 commit into from
Jun 30, 2026
Merged

docs: full-suite verification for interpreter-compat changes #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ source of truth for recipes — run `just --list` or read it. The non-obvious bi
the rest (the integration suites) do.
- `just lint` / `just lint-ci` — autofix vs non-mutating; `lint-ci` also runs the
planning-bundle validator (`planning/index.py --check`).
- Verifying a Python-version / interpreter-compat change: run the **full** suite
on the target interpreter (the CI matrix, or `just test` in docker), not just
the no-Redis subset. An integration-only failure — e.g. a broker-shutdown hang
that only bites under a specific interpreter's async timing — won't surface in
`test_unit.py` / `test_fake.py` alone.

## Workflow

Expand Down