litellm - 💡(How to fix) Fix litellm[proxy] Installation Problem [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26056Fetched 2026-04-19 15:06:05
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Timeline (top)
commented ×1

Error Message

Building wheel for orjson (pyproject.toml) ... error error: subprocess-exited-with-error error: failed to run custom build command for pyo3-ffi v0.23.3 (C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\include\pyo3\pyo3-ffi) error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.13) Error: command ['maturin', 'pep517', 'build-wheel', '-i', 'D:\Users\Clay\AppData\Local\Programs\Python\Python314\python.exe', '--compatibility', 'off'] returned non-zero exit status 1 note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for orjson error: failed-wheel-build-for-install

Root Cause

Caused by: process didn't exit successfully: C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\target\release\build\pyo3-ffi-91419c11a3caaa26\build-script-build (exit code: 1) --- stdout cargo:rustc-check-cfg=cfg(Py_LIMITED_API) cargo:rustc-check-cfg=cfg(Py_GIL_DISABLED) cargo:rustc-check-cfg=cfg(PyPy) cargo:rustc-check-cfg=cfg(GraalPy) cargo:rustc-check-cfg=cfg(py_sys_config, values("Py_DEBUG", "Py_REF_DEBUG", "Py_TRACE_REFS", "COUNT_ALLOCS")) cargo:rustc-check-cfg=cfg(invalid_from_utf8_lint) cargo:rustc-check-cfg=cfg(pyo3_disable_reference_pool) cargo:rustc-check-cfg=cfg(pyo3_leak_on_drop_without_reference_pool) cargo:rustc-check-cfg=cfg(diagnostic_namespace) cargo:rustc-check-cfg=cfg(c_str_lit) cargo:rustc-check-cfg=cfg(rustc_has_once_lock) cargo:rustc-check-cfg=cfg(io_error_more) cargo:rustc-check-cfg=cfg(fn_ptr_eq) cargo:rustc-check-cfg=cfg(Py_3_7) cargo:rustc-check-cfg=cfg(Py_3_8) cargo:rustc-check-cfg=cfg(Py_3_9) cargo:rustc-check-cfg=cfg(Py_3_10) cargo:rustc-check-cfg=cfg(Py_3_11) cargo:rustc-check-cfg=cfg(Py_3_12) cargo:rustc-check-cfg=cfg(Py_3_13) cargo:rerun-if-env-changed=PYO3_CROSS cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG cargo:rerun-if-env-changed=PYO3_USE_ABI3_FORWARD_COMPATIBILITY

RAW_BUFFERClick to expand / collapse

I'm trying to install litellm[proxy] in Python 3.14 and failed. log as below:

Building wheels for collected packages: orjson
  Building wheel for orjson (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for orjson (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [79 lines of output]
      Running `maturin pep517 build-wheel -i D:\Users\Clay\AppData\Local\Programs\Python\Python314\python.exe --compatibility off`
      📦 Including license file `LICENSE-APACHE`
      📦 Including license file `LICENSE-MIT`
      🍹 Building a mixed python/rust project
      🔗 Found pyo3-ffi bindings
      🐍 Found CPython 3.14 at D:\Users\Clay\AppData\Local\Programs\Python\Python314\python.exe
         Compiling target-lexicon v0.13.1
         Compiling proc-macro2 v1.0.92
         Compiling unicode-ident v1.0.14
         Compiling once_cell v1.20.2
         Compiling serde v1.0.217
         Compiling rustversion v1.0.19
         Compiling shlex v1.3.0
         Compiling cfg-if v1.0.0
         Compiling libc v0.2.169
         Compiling itoa v1.0.14
         Compiling ryu v1.0.18
         Compiling serde_json v1.0.135
         Compiling version_check v0.9.5
         Compiling memchr v2.7.4
         Compiling static_assertions v1.1.0
         Compiling cc v1.2.1
         Compiling half v2.4.1
         Compiling encoding_rs v0.8.35
         Compiling bytecount v0.6.8
         Compiling jiff v0.1.21
         Compiling uuid v1.11.0
         Compiling xxhash-rust v0.8.15
         Compiling simdutf8 v0.1.5
         Compiling associative-cache v2.0.0
         Compiling smallvec v1.13.2
         Compiling itoap v1.0.1
         Compiling quote v1.0.38
         Compiling castaway v0.2.3
         Compiling pyo3-build-config v0.23.3 (C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\include\pyo3\pyo3-build-config)
         Compiling syn v2.0.95
         Compiling pyo3-ffi v0.23.3 (C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\include\pyo3\pyo3-ffi)
         Compiling orjson v3.10.15 (C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec)
      error: failed to run custom build command for `pyo3-ffi v0.23.3 (C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\include\pyo3\pyo3-ffi)`

      Caused by:
        process didn't exit successfully: `C:\Users\Clay\AppData\Local\Temp\pip-install-y947v9jh\orjson_a25d0183f128422f90a239c8175ca0ec\target\release\build\pyo3-ffi-91419c11a3caaa26\build-script-build` (exit code: 1)
        --- stdout
        cargo:rustc-check-cfg=cfg(Py_LIMITED_API)
        cargo:rustc-check-cfg=cfg(Py_GIL_DISABLED)
        cargo:rustc-check-cfg=cfg(PyPy)
        cargo:rustc-check-cfg=cfg(GraalPy)
        cargo:rustc-check-cfg=cfg(py_sys_config, values("Py_DEBUG", "Py_REF_DEBUG", "Py_TRACE_REFS", "COUNT_ALLOCS"))
        cargo:rustc-check-cfg=cfg(invalid_from_utf8_lint)
        cargo:rustc-check-cfg=cfg(pyo3_disable_reference_pool)
        cargo:rustc-check-cfg=cfg(pyo3_leak_on_drop_without_reference_pool)
        cargo:rustc-check-cfg=cfg(diagnostic_namespace)
        cargo:rustc-check-cfg=cfg(c_str_lit)
        cargo:rustc-check-cfg=cfg(rustc_has_once_lock)
        cargo:rustc-check-cfg=cfg(io_error_more)
        cargo:rustc-check-cfg=cfg(fn_ptr_eq)
        cargo:rustc-check-cfg=cfg(Py_3_7)
        cargo:rustc-check-cfg=cfg(Py_3_8)
        cargo:rustc-check-cfg=cfg(Py_3_9)
        cargo:rustc-check-cfg=cfg(Py_3_10)
        cargo:rustc-check-cfg=cfg(Py_3_11)
        cargo:rustc-check-cfg=cfg(Py_3_12)
        cargo:rustc-check-cfg=cfg(Py_3_13)
        cargo:rerun-if-env-changed=PYO3_CROSS
        cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
        cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
        cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
        cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG
        cargo:rerun-if-env-changed=PYO3_USE_ABI3_FORWARD_COMPATIBILITY

        --- stderr
        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.3
        = 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...
      💥 maturin failed
        Caused by: Failed to build a native library through cargo
        Caused by: Cargo build finished with "exit code: 101": `"cargo" "rustc" "--profile" "release" "--message-format" "json-render-diagnostics" "--manifest-path" "C:\\Users\\Clay\\AppData\\Local\\Temp\\pip-install-y947v9jh\\orjson_a25d0183f128422f90a239c8175ca0ec\\Cargo.toml" "--lib"`
      Error: command ['maturin', 'pep517', 'build-wheel', '-i', 'D:\\Users\\Clay\\AppData\\Local\\Programs\\Python\\Python314\\python.exe', '--compatibility', 'off'] returned non-zero exit status 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for orjson
Failed to build orjson
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> orjson```
By the way, I've already installed orjson 3.11.8 in the environment. what should I do for fixing?

extent analysis

TL;DR

The issue is likely due to PyO3's maximum supported Python version being 3.13, which is lower than the installed Python 3.14, and can be fixed by setting an environment variable to suppress this check or by downgrading Python to a supported version.

Guidance

  • The error message indicates that the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.13), which is the likely cause of the issue.
  • To verify this, check the PyO3 version and the Python version installed in the environment.
  • To mitigate this issue, set the environment variable PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress the version check and build anyway using the stable ABI.
  • Alternatively, consider downgrading Python to a version supported by PyO3 (e.g., Python 3.13) to ensure compatibility.

Example

No code snippet is provided as the issue is related to environment configuration and package compatibility.

Notes

The provided solution is based on the information given in the error message and may not be applicable in all scenarios. It is recommended to check for updates to PyO3 and orjson packages that may support Python 3.14.

Recommendation

Apply the workaround by setting PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress the version check, as downgrading Python may not be feasible or desirable in all cases. This allows the build to proceed using the stable ABI, potentially resolving the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix litellm[proxy] Installation Problem [1 comments, 2 participants]