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
36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
<!--
|
|
The agent's INPUT for Module 25. This is a well-formed issue in the Module 9 format: title,
|
|
context, acceptance criteria, scope. It is deliberately a good candidate for an agent: well-
|
|
scoped, concrete, and it mirrors a pattern already in the codebase (the existing `done` command).
|
|
|
|
The orchestrator (agent_runner.py) reads this file and pairs it with your committed AI config
|
|
(Module 5) to build the agent's brief. Edit it and you change what the agent attempts.
|
|
-->
|
|
|
|
# Add a `delete <index>` command to the CLI
|
|
|
|
**Type:** feature · **Priority:** p2 · **Labels:** `cli`, `ready`, `agent`
|
|
|
|
## Context
|
|
|
|
`tasks-app` can `add`, `list`, and mark a task `done`, but there's no way to remove a task. Once a
|
|
task is added by mistake it stays forever. The `done` command already takes an index and mutates the
|
|
list through a method on `TaskList`, so a `delete` command should follow the exact same shape. This
|
|
is a patterned change, not a design problem.
|
|
|
|
## Acceptance criteria
|
|
|
|
- `python3 cli.py delete <index>` removes the task at that 0-based index and saves the list.
|
|
- After deleting, the remaining tasks keep their relative order.
|
|
- `delete` with an out-of-range or non-integer index prints a clear error (e.g.
|
|
`no task at index 99`) and exits non-zero, instead of dumping a traceback.
|
|
- The logic lives on `TaskList` (a `remove(index)` method or equivalent), mirroring how `complete`
|
|
works; `cli.py` only parses arguments and calls it.
|
|
- A test covers: a successful delete removes the right task, and an out-of-range delete is handled.
|
|
|
|
## Out of scope
|
|
|
|
- Changing how tasks are stored or numbered.
|
|
- Bulk delete, undo, or a confirmation prompt.
|
|
- Reworking the existing `add` / `list` / `done` commands.
|