-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
enhancementNew feature or requestNew feature or requestv0.14.3Targeted for v0.14.3 releaseTargeted for v0.14.3 release
Description
Summary
Evaluate adopting uv as the Python dependency manager, replacing pip in Dockerfiles and CI.
Context
In #280 we consolidated Python dependencies to pyproject.toml (PEP 621) with requirements.txt and requirements-test.txt as generated files consumed by Docker and CI. pip is used for all installs.
uv would provide:
- Lockfile (
uv.lock) for reproducible installs - Faster installs in Docker builds and CI
uv sync --group testto install dependency groups directly frompyproject.tomlwithout maintaining separate requirements filesuv exportto generate requirements files if needed for compatibility
Trade-offs
- Adds a new tool dependency (needs to be installed in Dockerfiles and CI)
- pip works fine for our scale (3 runtime deps, 5 test deps)
- uv is moving fast but is now widely adopted
Acceptance criteria
- Evaluate whether uv simplifies the Docker build or adds unnecessary complexity
- If adopting: update Dockerfiles, CI, and Makefile to use uv
- If adopting: commit
uv.lockfor reproducible installs - If deferring: document decision and close
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestv0.14.3Targeted for v0.14.3 releaseTargeted for v0.14.3 release