Skip to content

Conversation

@jstasiak
Copy link

I thought this could be useful (I'm biased, I use uv everywhere) and should make the developer and user experience nicer:

  • No manual venv management
  • No Python version mismatch problems
  • Precise dependency versions including transitive dependencies
  • Fewer things to document

The uv sync step can be skipped, actually, as uv run triggers it implicitly, but I kept it for clarity.

How I made this change:

  1. uv add -r requirements.txt.
  2. Make some adjustments to pyproject.toml, copy comments from requirements.txt.
  3. Adjust the readme to match.

I thought this could be useful (I'm biased, I use uv everywhere) and
should make the developer and user experience nicer:

* No manual venv management
* No Python version mismatch problems
* Precise dependency versions including transitive dependencies
* Fewer things to document

The uv sync step can be skipped, actually, as uv run triggers it
implicitly, but I kept it for clarity.

How I made this change:

1. uv add -r requirements.txt.
2. Make some adjustments to pyproject.toml, copy comments from
   requirements.txt.
3. Adjust the readme to match.
@jstasiak jstasiak changed the title Use uv for project management Use uv for Python project management Dec 31, 2025
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.

1 participant