Switch from pip to uv #747
Assignees
Comments
|
yesss! we would really like to get on to |
ashwinb
added a commit
that referenced
this issue
Feb 1, 2025
## What does this PR do? See issue: #747 -- `uv` is just plain better. This PR does the bare minimum of replacing `pip install` by `uv pip install` and ensuring `uv` exists in the environment. ## Test Plan First: create new conda, `uv pip install -e .` on `llama-stack` -- all is good. Next: run `llama stack build --template together` followed by `llama stack run together` -- all good Next: run `llama stack build --template together --image-name yoyo` followed by `llama stack run together --image-name yoyo` -- all good Next: fresh conda and `uv pip install -e .` and `llama stack build --template together --image-type venv` -- all good. Docker: `llama stack build --template together --image-type container` works!
|
Closed via #921 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🚀 Describe the new functionality needed
uv has great performance boost https://github.com/astral-sh/uv
A couple of projects started adopting it, e.g. vLLM: https://blog.vllm.ai/2025/01/10/dev-experience.html
💡 Why is this needed? What if we don't build it?
Performance improvement
Other thoughts
No response
The text was updated successfully, but these errors were encountered: