Add support for uv as package manager #218
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Updated the PR. I now choose the cache dir to point to the agent.venvs_dir path. That should ensure that venvs are cached between invocations. UV creates a .venv dir in the root of the project, so that's also accounted. for. @jkhenning @bmartinn for visibility. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses #214 by supporting uv as package manager similar to how it's done for poetry today.
It does not change the default behaviour of pip, although that could also be done.
I have a single TODO that I'm unsure of. In commands/worker.py, line 3457, I would like to set UV_PROJECT_ENVIRONMENT to the current venv cache dir. What should that be?