Use compileall for recursive compile checks
Stop letting the explicit compile step overstate its coverage. The old py_compile globs only touched top-level modules, so syntax errors in nested packages could slip past make check and release-check.\n\nAdd a shared compile-check recipe in Makefile that runs python -m compileall -q src tests, and have both check and release-check use it so the local verification paths stay aligned. Update the GitHub Actions compile step and the matching runtime validation evidence doc to describe the same recursive compile contract.\n\nValidate with python3 -m compileall -q src tests, make check, and make release-check.
This commit is contained in:
parent
94ead25737
commit
f779b71e1b
3 changed files with 10 additions and 6 deletions
|
|
@ -15,8 +15,9 @@ Completed on 2026-03-12:
|
|||
- `PYTHONPATH=src python3 -m unittest discover -s tests -p 'test_*.py'`
|
||||
- confirms the runtime and diagnostics changes do not regress the broader
|
||||
daemon, CLI, config, and portable bundle flows
|
||||
- `python3 -m py_compile src/*.py tests/*.py`
|
||||
- verifies the updated runtime and diagnostics modules compile cleanly
|
||||
- `python3 -m compileall -q src tests`
|
||||
- verifies the updated runtime, diagnostics, and nested package modules
|
||||
compile cleanly
|
||||
|
||||
## Automated scenario coverage
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue