Skip to content

Commit 259a3c4

Browse files
Technologicatclaude
andcommitted
CLAUDE.md: replace venv activation rule with pdm run note
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent deab4c6 commit 259a3c4

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

CLAUDE.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,10 @@ Uses PDM with `pdm-backend`. Python 3.10–3.14, also PyPy 3.11.
2222
# Set up development environment
2323
pdm install # creates .venv/ and installs deps
2424
pdm use --venv in-project
25-
source .venv/bin/activate
2625
```
2726

27+
Prefix commands with `pdm run` if the venv is not active.
28+
2829
The project venv is managed by PDM (`pdm venv create`, `pdm use --venv in-project`). To switch Python versions, remove the old venv and create a new one:
2930

3031
```bash
@@ -42,7 +43,7 @@ pdm install
4243
Custom test framework (`unpythonic.test.fixtures`, not pytest). Tests use macros (`test[]`, `test_raises[]`) and conditions/restarts for reporting. The test runner does not need the `macropython` wrapper—it activates macros via `import mcpyrate.activate`. Note: test *framework* is at `unpythonic/test/` (singular); actual *tests* are in `tests/` (plural) subdirectories.
4344

4445
```bash
45-
# Run all tests (from repo root, with venv activated)
46+
# Run all tests (from repo root)
4647
python runtests.py
4748

4849
# Run a single test module directly

0 commit comments

Comments
 (0)