Hardens sandbox isolation for PythonInterpreter
DSPy releases 3.3.1 with hardened sandbox isolation and optional managed runtime for PythonInterpreter.
DSPy 3.3.1 DSPy 3.3.1 contains many interpreter fixes and improvements. It makes `PythonInterpreter` easier to install, substantially strengthens sandbox isolation and request handling, and adds end-to-end visibility into interpreter execution. The release also improves optimizer throughput, adapter correctness, and MCP compatibility. Highlights PythonInterpreter: Managed Runtime, Hardening, and Lifecycle Visibility Installation, isolation, and execution integrity `PythonInterpreter` now has an optional managed runtime installation: ```bash pip install "dspy[deno]" ``` DSPy prefers that managed binary when present, while continuing to support system Deno 2.x and an explicit custom `deno_command`.
The default path pins Pyodide, validates Deno `>=2.0.0,<3.0.0`, and ignores ambient Node and Deno project configuration so nearby application files cannot change sandbox startup. The interpreter also closes several execution-integrity and isolation gaps: unsolicited sandbox diagnostics can no longer desynchronize JSON-RPC replies; request IDs are unpredictable, and recursive execution through one of an interpreter's own host tools is rejected; bundled runtime files are protected and…
- github.comDSPy v3.3.1primary