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
..
__init__.py	API Updates (#73)	2024-09-17 19:51:35 -07:00
_build.py	Use uv pip install instead of pip install (#921)	2025-01-31 22:29:41 -08:00
build.py	Add --print-deps-only for computing dependencies	2025-01-31 14:33:51 -08:00
configure.py	More generic image type for OCI-compliant container technologies (#802)	2025-01-17 16:37:42 -08:00
list_apis.py	API Updates (#73)	2024-09-17 19:51:35 -07:00
list_providers.py	provider_id => provider_type, adapter_id => adapter_type	2024-10-02 14:05:59 -07:00
run.py	Fix running stack built with base conda environment (#903)	2025-01-29 21:24:22 -08:00
stack.py	add --version to llama stack CLI & /version endpoint (#732)	2025-01-08 16:30:06 -08:00