serve the install.sh test fixtures from Go, not Python's http.server #626

New issue

Open

opened 2026-09-24 18:36:06 +00:00 by hexajon · 0 comments

hexajon commented

2026-09-24 18:36:06 +00:00

Owner

What

scripts/test-install-sh.sh tests the curl-pipe installer, which is why it stays bash. But it serves its fixtures with python3 -m http.server on a loopback port, and it refuses to run without python3. That is the only reason the test needs Python.

Fix

A madtea-dev subcommand serves a directory over HTTP on 127.0.0.1 at a given port, and exits when stopped.
test-install-sh.sh uses it in place of python3 -m http.server, and the python3 requirement check goes.

Acceptance

scripts/test-install-sh.sh passes with no python3 on the PATH.
The server binds loopback only.

## What `scripts/test-install-sh.sh` tests the curl-pipe installer, which is why it stays bash. But it serves its fixtures with `python3 -m http.server` on a loopback port, and it refuses to run without `python3`. That is the only reason the test needs Python. ## Fix - A `madtea-dev` subcommand serves a directory over HTTP on `127.0.0.1` at a given port, and exits when stopped. - `test-install-sh.sh` uses it in place of `python3 -m http.server`, and the `python3` requirement check goes. ## Acceptance - `scripts/test-install-sh.sh` passes with no `python3` on the PATH. - The server binds loopback only.

hexajon added the

refactoring

testing

labels

2026-09-24 18:36:06 +00:00

hexajon referenced this issue

2026-09-24 18:36:41 +00:00

Epic: no Python in the repo #630

hexajon added a new dependency

2026-09-24 18:36:49 +00:00

#630 Epic: no Python in the repo