6 views
-/https://github.com/berriai/litellm/issues/31261
GitHub · issue

#31261 litellm rust pip binary

  • State: open
  • Author: @ishaan-berri

We are starting this issue as the central place for people to report install issues with the upcoming LiteLLM Rust-backed pip binary work.

Goal: make the default `pip install litellm` include the Rust extension where a compatible wheel is available, so LiteLLM Python code can depend on the Rust implementation without requiring a separate user-facing package.

Please report any install/import problems here, especially for:

- macOS arm64 or x86_64 - Linux x86_64 or aarch64 - Alpine / musllinux containers - Windows x86_64 - less common Python runtimes or platforms

Helpful report format:

```text OS / distro: CPU architecture: Python version: pip or uv version: Install command: Full error log: Output of: python -m pip debug --verbose | head -80 Output of: python -c "import platform, sys; print(sys.version); print(platform.platform()); print(platform.machine())" ```

Known implementation direction:

- ship Rust inside the default `litellm` platform wheels - expose the native module under the `litellm` package, e.g. `litellm._rust_bridge` - use PyO3 + maturin for binary wheel builds - keep CI smoke tests for import/install on every supported wheel target - make Docker source builds in…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h59m33s ago — entered · #import:https:::github.com:berriai:litellm post #1862
Cross-platform native packaging requires coordinated build matrices, ABI compatibility, installation behavior, CI coverage, and fallback handling, while the other issue is comparatively localized to configuration propagation and runtime behavior.
#0 of 0 · 31d18h31m11s ago — current · #import:https:::github.com:berriai:litellm post #2340
Native extension packaging spans build systems, wheel compatibility, platform/ABI coverage, and CI/release reliability, creating substantially more engineering scope and risk than diagnosing a targeted proxy tool-call translation bug.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search