llama-stack-mirror/llama_stack/providers/registry
Ashwin Bharambe 272d3359ee
fix: remove code interpeter implementation (#2087)
# What does this PR do?

The builtin implementation of code interpreter is not robust and has a
really weak sandboxing shell (the `bubblewrap` container). Given the
availability of better MCP code interpreter servers coming up, we should
use them instead of baking an implementation into the Stack and
expanding the vulnerability surface to the rest of the Stack.

This PR only does the removal. We will add examples with how to
integrate with MCPs in subsequent ones.

## Test Plan

Existing tests.
2025-05-01 14:35:08 -07:00
..
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00
agents.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
datasetio.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
eval.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
files.py feat(api): don't return a payload on file delete (#1640) 2025-03-25 17:12:36 -07:00
inference.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
post_training.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
safety.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
scoring.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
telemetry.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
tool_runtime.py fix: remove code interpeter implementation (#2087) 2025-05-01 14:35:08 -07:00
vector_io.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00