Check at startup that the launcher's Python can read zstd files, and say how to fix it when it cannot.

Run from a checkout, the launcher uses the Python that started it. A Python older than 3.14 without the zstandard
package got through the first-run screen and stopped at Gather Build Tools with only "No module named 'zstandard'",
after the packages were downloaded. toolchain.zstd_missing now looks for compression.zstd or zstandard when the
launcher starts. Without either, the log and the first screen name the Python and give the pip line for
tools/requirements-launcher.txt, and Gather Build Tools stops with the same message before it unpacks anything. A
release's own Python always has the package; if it ever lacks it, the message says to reinstall NX2navi.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 07:16:14 -05:00
parent ee46a19ede
commit d2ab9a00be
6 changed files with 48 additions and 0 deletions

View File

@@ -99,6 +99,12 @@ for updates); an XInput gamepad (d-pad or left stick, A, B, Y) while the window
`python -m launcher --selftest --shots DIR` draws every screen with made-up states and saves a PNG of each.
Run from a checkout, the launcher and the build use the Python that started it, which needs the packages of
`tools/requirements-launcher.txt`. At startup the launcher checks that this Python can read zstd files
(`toolchain.zstd_missing`: Python 3.14's `compression.zstd`, or the `zstandard` package). If it cannot, the first screen
and the log say so and give the `pip install` line, and Gather Build Tools stops with the same message before it
unpacks anything.
## The launcher's folder
```