llama-stack/llama_stack
Ashwin Bharambe 5b1e69e58e
Use uv pip install instead of pip install (#921)
## 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!
2025-01-31 22:29:41 -08:00
..
apis fix ImageContentItem to take base64 string as image.data (#909) 2025-01-30 15:58:23 -08:00
cli Use uv pip install instead of pip install (#921) 2025-01-31 22:29:41 -08:00
distribution Use uv pip install instead of pip install (#921) 2025-01-31 22:29:41 -08:00
providers Update client-sdk test config option handling 2025-01-31 15:37:25 -08:00
scripts Use uv pip install instead of pip install (#921) 2025-01-31 22:29:41 -08:00
templates Use uv pip install instead of pip install (#921) 2025-01-31 22:29:41 -08:00
__init__.py export LibraryClient 2024-12-13 12:08:00 -08:00