Skip to content

Switch to uv for dependency management#48

Open
dmacvicar wants to merge 3 commits intomainfrom
feature/uv-migration
Open

Switch to uv for dependency management#48
dmacvicar wants to merge 3 commits intomainfrom
feature/uv-migration

Conversation

@dmacvicar
Copy link
Contributor

@dmacvicar dmacvicar commented Mar 18, 2026

  • Replace pip + requirements.txt with uv for faster installs and lockfile-based reproducibility
  • Move dependencies to pyproject.toml, update Makefile and CI workflows to use uv sync/run

@github-actions
Copy link

github-actions bot commented Mar 18, 2026

Terraform Test Results

2 tests   1 ✅  33s ⏱️
1 suites  0 💤
1 files    1 ❌

For more details on these failures, see this check.

Results for commit aa5a640.

♻️ This comment has been updated with latest results.

@dmacvicar dmacvicar force-pushed the feature/uv-migration branch from eeb7349 to aa5a640 Compare March 18, 2026 10:23
@dmacvicar dmacvicar changed the title Migrate from pip to uv for dependency management Switch to uv for dependency management Mar 18, 2026
@dmacvicar dmacvicar marked this pull request as ready for review March 18, 2026 10:31
@dmacvicar dmacvicar requested a review from macnev2013 March 18, 2026 10:31
Replace pip + requirements.txt with uv for faster installs and
lockfile-based reproducibility. Move dependencies to pyproject.toml,
update Makefile and CI workflows to use uv sync/run.
@dmacvicar dmacvicar force-pushed the feature/uv-migration branch from aa5a640 to 9c50027 Compare March 18, 2026 15:02
Copy link
Collaborator

@macnev2013 macnev2013 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Just a minor comment regarding the virutalenv.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The venv target and VENV_DIR/VENV_RUN variables can be removed — uv sync automatically creates and manages the .venv, and uv run handles activation implicitly. The install target doesn't need venv as a dependency, and prepare-organizations can use uv run instead of manually sourcing the activate script.

uv sync already creates and manages .venv, and uv run handles
activation implicitly, so the venv target and VENV_DIR/VENV_RUN
variables are unnecessary.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants