The README's test setup installs the way CI does

[HughRunyan]

Addresses the Copilot comment left unresolved on #61.

The problem

The Tests block told a contributor to run a bare pip install -e . immediately after installing the pinned lockfile:

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

setup.py's install_requires comes from requirements.in — the abstract deps a consumer gets — so pip re-resolves exactly what requirements.txt had just pinned. A contributor following the README ends up on a different dependency set from CI, which is the failure mode a lockfile exists to prevent.

CI already gets this right, and says why in a comment:

Editable, --no-deps: makes import SWEET_python resolve to this checkout without re-resolving what requirements.txt just pinned

So the README was the one place giving the advice CI's own comment warns against.

What changed

--no-deps on the editable install in the Tests block, plus the reason in prose so the flag does not look like noise a future edit can drop.

The pip install -e . under Installation is deliberately left alone. That is the consumer path — no lockfile to protect, and it should resolve its dependencies.

Acceptance criteria

• The README's test setup produces the same environment as .github/workflows/tests.yml.
• The reason for --no-deps is written down where the command is.
• The consumer install path is unchanged.
• No code, model or output change.

Definition of done

• Acceptance criteria met
• Checks pass (documentation only)
• Docs updated — this PR is the doc change; no changelog entry, matching pytest runs in CI on every push and pull request #61, which was likewise CI/tooling rather than model behaviour
• Reviewed and merged

🤖 Generated with Claude Code