llama-stack/llama_stack/cli
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
..
model Convert SamplingParams.strategy to a union (#767) 2025-01-15 05:38:51 -08:00
scripts API Updates (#73) 2024-09-17 19:51:35 -07:00
stack Use uv pip install instead of pip install (#921) 2025-01-31 22:29:41 -08:00
tests Rename all inline providers with an inline:: prefix (#423) 2024-11-11 22:19:16 -08:00
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00
download.py Added optional md5 validate command once download is completed (#486) 2024-11-19 17:42:43 -08:00
llama.py Add a verify-download command to llama CLI (#457) 2024-11-14 11:47:51 -08:00
subcommand.py API Updates (#73) 2024-09-17 19:51:35 -07:00
table.py API Updates (#73) 2024-09-17 19:51:35 -07:00
verify_download.py Sec fixes as raised by bandit (#917) 2025-01-31 13:44:26 -08:00