llama-stack-mirror/llama_stack/providers/registry
Charlie Doern 41431d8bdd refactor: convert providers to be installed via package
currently providers have a `pip_package` list. Rather than make our own form of python dependency management, we should use `pyproject.toml` files in each provider declaring the dependencies in a more trackable manner.
Each provider can then be installed using the already in place `module` field in the ProviderSpec, pointing to the directory the provider lives in
we can then simply `uv pip install` this directory as opposed to installing the dependencies one by one

Signed-off-by: Charlie Doern <cdoern@redhat.com>
2025-09-22 09:23:50 -04:00
..
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00
agents.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
batches.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
datasetio.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
eval.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
files.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
inference.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
post_training.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
safety.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
scoring.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
telemetry.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
tool_runtime.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00
vector_io.py refactor: convert providers to be installed via package 2025-09-22 09:23:50 -04:00