[HyperionBurn]

What

The migration to uv in #1472 removed the root requirements.txt, but two references to it were left behind:

• docs/contributing.md — the "install typer inside the container" step
• scripts/docker/Dockerfile — the final RUN step

Because scripts/docker/compose.yaml builds directly from that Dockerfile:

build:
  context: ../../

  dockerfile: scripts/docker/Dockerfile

docker compose run typer bash currently fails while building the image, because the file the RUN step reads no longer exists. That is the documented entry point for testing shell completion, so the whole workflow is blocked at the first command.

This replaces both with uv pip install -e ..

Why uv pip install -e . and not uv sync

The deleted requirements.txt was:

-e .

-r requirements-tests.txt
-r requirements-docs.txt

prek>=0.2.24,<1.0.0

So the previous behaviour was an editable install of the project itself into the container's Python, plus the test/docs/prek extras. The Dockerfile sets ENV UV_SYSTEM_PYTHON=1, which is what makes uv pip install target the system interpreter — that is how typer ended up on PATH, which the rest of the guide depends on for typer --install-completion and typer demo.py <TAB>.

uv pip install -e . preserves that exactly. I deliberately did not use uv sync, because it creates a project virtualenv at /code/.venv and would leave typer off PATH for the steps that follow in the guide. The test/docs/prek extras are not needed here — this container is only used to exercise shell completion.

How this was verified

• Confirmed requirements.txt is absent from master and from the working tree.
• Confirmed its removal: commit 39353af ("⬆️ Migrate to uv", ⬆️ Migrate to uv #1472) shows requirements.txt [removed] along with requirements-tests.txt, requirements-docs.txt and requirements-docs-tests.txt. That same commit already updated the other install section in docs/contributing.md to uv sync, but did not touch the container guide or the Dockerfile.
• Read the file's contents at its parent commit a6a2a37 to confirm it started with -e ..
• Grepped the tree for any remaining requirements.txt reference; only the historical entry in docs/release-notes.md remains, which is correct as a changelog record.
• Checked that no open PR or issue already covers this.

Only two lines change.

[github-actions]

📝 Docs preview

Last commit 7963544 at: https://66557a93.typertiangolo.pages.dev

Modified Pages

• https://66557a93.typertiangolo.pages.dev/contributing/ - (before)

[svlandeg]

Thanks for the PR! For future reference, please follow the contribution guidelines by opening a discussion thread first, and declaring AI usage (incl if none).

Anyway this looks good to me, but pinging @DoctorJohn whether he can sign of on this 🙏

[DoctorJohn]

The original requirements.txt file also installed the tests and docs dependency groups. So technically, we should either go with:

Suggested change

	RUN uv pip install -e .
	RUN uv sync

or, if we want to use the pip interface:

Suggested change

	RUN uv pip install -e .
	RUN uv pip install --group tests --group docs --editable .

I'd go with the first option, which syncs the projects dependencies and the dev dependency group, which also includes the tests and docs dependency groups.
Tho, I must admit I'm not even sure this Dockerfile is even used anymore.