Skip to content

Conversation

@reece
Copy link
Member

@reece reece commented Aug 18, 2025

This PR starts the migration to uv for python dev tooling by creating the venv with uv and using it to specify a specific Python version.

To eval this PR, please follow the steps in the README for developers.

@reece reece requested a review from a team as a code owner August 18, 2025 14:15
This was linked to issues Aug 18, 2025
@jsstevenson
Copy link
Contributor

jsstevenson commented Aug 18, 2025

👍 Two general ideas for your consideration:

  1. use uv sync instead of uv pip install. The main difference I'm aware of is that uv sync will remove extraneously-installed packages from the environment. This honestly kinda bugs me sometimes but I can see an argument for employing it.

  2. use uv run to perform the other entrypoint-based actions (pytest ruff etc). This actually removes the need to have the virtualenv activated (although I think it's generally a good idea to stay within one anyway). This might be out of scope of this ticket though.

oh, also, just from googling... https://github.com/tox-dev/tox-uv ? maybe?

korikuzma
korikuzma previously approved these changes Aug 18, 2025
@reece reece closed this Aug 28, 2025
@reece reece deleted the 62-adopt-uv-as-pyenv-declaration branch August 28, 2025 04:36
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.

adopt uv for venv generation adopt uv as pip replacement

4 participants