justin
3221f7abe8
CI / check (pull_request) Successful in 7s
Most current systems (default Debian/Ubuntu, recent macOS) install Python only as `python3`, with no bare `python` on PATH, so learners who copied `python cli.py ...` into their host shell hit "command not found". Convert host-shell `python <cmd>` -> `python3 <cmd>` across module/lab READMEs, lab `.py` docstrings & usage strings, blog posts, lab prompt and instruction files, the M04 verify.sh message, and the M10/M24 lab patches. Module 01's convention note (and its blog/02 mirror) is rewritten so `python3` is canonical and `python` is the documented fallback. Stop-lines respected: Docker image tags (`python:3.12-slim`), `.venv/.../python` and `...\.venv\Scripts\python.exe` paths, the M20 `"command": "python"` teaching example and surrounding venv prose, container-internal invocations (M16/M18 Dockerfiles, M16 README `docker run` examples), and CI-workflow `run:` steps fed by `actions/setup-python` / `image: python:3.12` are left as `python` on purpose. pip was left out of scope: most occurrences are prose or CI/container-internal, and `pip3` does not fix the PEP 668 externally-managed-environment refusal that the course already addresses with venvs. The M01 note is worded to stay consistent with bare `pip` (use whichever pip pairs with your Python). Build (tools/build_wiki.py) and tools/check.sh both pass. Closes #104 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GAEzanEoGJT5o1VizQar47
26 lines
1019 B
Markdown
26 lines
1019 B
Markdown
<!--
|
|
Module 11 lab: the issue to file (the "contract" / station 1 of the loop).
|
|
|
|
Create a new issue on your git host. Paste the line below as the TITLE and everything under
|
|
"Body" as the issue description. Note the number the host assigns it (e.g. #42); every later
|
|
step references it. Assign it to yourself for the first run-through.
|
|
-->
|
|
|
|
Title: Add a `clear-done` command to remove completed tasks
|
|
|
|
Body:
|
|
|
|
**What**
|
|
Add a `clear-done` command to the tasks CLI that removes every task already marked done, leaving
|
|
the pending ones untouched.
|
|
|
|
**Why**
|
|
After working through a list, the completed items pile up as noise. There's currently no way to
|
|
clear them out short of editing `tasks.json` by hand.
|
|
|
|
**Acceptance criteria**
|
|
- `python3 cli.py clear-done` removes all completed tasks and keeps all pending ones.
|
|
- It prints how many tasks were removed.
|
|
- The removal logic lives in `tasks.py` (a `TaskList` method), not in `cli.py`.
|
|
- Running it when nothing is done is a no-op that removes 0 tasks (no crash).
|