Skip to content

The README's test setup installs the way CI does #64

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
HughRunyan merged 1 commit into from
Sep 9, 2026
Merged

The README's test setup installs the way CI does #64

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
10 changes: 9 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,18 @@ The test suite lives in `tests/` and runs with pytest:

```
pip install -r requirements.txt "pytest>=8,<10"
pip install -e .
pip install --no-deps -e .
pytest
```

`--no-deps` on the editable install is the point of the two lines above it:
`setup.py`'s `install_requires` comes from `requirements.in`, the abstract deps,
so without it pip re-resolves what `requirements.txt` just pinned and the local
environment stops matching CI. The install step in
`.github/workflows/tests.yml` is the same three commands for the same reason.
(The `pip install -e .` in Installation above has no lockfile to protect and
should resolve its dependencies.)

Every test in the suite is hermetic — no database, no network, no environment
variables — and the whole thing takes a few seconds.

Expand Down