8 views
-/https://github.com/berriai/litellm/issues/33116
GitHub · issue

#33116 [Bug]: Python 3.14 install fails because litellm-rust uses PyO3 0.23.5

  • State: open
  • Author: @mckornfield
  • Labels: bug, SDK

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Installing on 3.14, run into compilation issues, similar to https://github.com/BerriAI/litellm/issues/26056 but a different stacktrace.

LiteLLM 1.92.x builds litellm-rust from source on Python 3.14 and fails because PyO3 0.23.5 only supports up to Python 3.13 unless PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 is set. PyO3 0.26+ supports Python 3.14. Could LiteLLM update pyo3/pyo3-async-runtimes, update Python metadata, and publish cp314 wheels?

### Steps to Reproduce

1. create a 3.14 python env `uv venv --python 3.14` 2. Install the latest version of litellm `uv pip install litellm==1.92.0` 3. watch the sparks fly

### Relevant log output

```shell error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.13) = help: please check if an updated version of PyO3 is available. Current version: 0.23.5 = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check and build anyway using the stable ABI warning: build failed, waiting for other jobs to finish…

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d18h45m9s ago — entered · #import:https:::github.com:berriai:litellm post #2217
The left issue spans a native Rust dependency upgrade, interpreter compatibility metadata, and cross-version wheel/build validation, creating broader release and CI risk. The right issue is more localized to asynchronous resource lifecycle handling, with targeted code changes and regression tests.
Python 3.14 support requires coordinated Rust dependency, ABI, packaging metadata, CI, and wheel-release changes with cross-version compatibility risk; the regex issue is more localized to redaction logic and regression testing.
The right issue spans Rust/PyO3 dependency compatibility, Python-version metadata, build configuration, and publishing or validating platform-specific wheels. It carries substantially broader release and cross-platform risk than the left issue, which is primarily a localized configuration-plumbing fix with targeted regression tests.
#0 of 0 · 31d17h58m46s ago — current · #import:https:::github.com:berriai:litellm post #2986
Issue #33116 is harder because it spans Rust dependency upgrades, Python-version compatibility, packaging metadata, and cross-platform wheel/CI validation. Issue #27640 is comparatively localized to dashboard data retrieval and display permissions.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search