18 views
-/https://github.com/berriai/litellm/issues/25210
GitHub · issue

#25210 [Bug]: python-dotenv pinned to ==1.0.1 since v1.83.1 causes dependency conflicts for library consumers

  • State: open
  • Author: @yudelevi

### Check for existing issues

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

### What happened?

Since `litellm==1.83.1`, the `python-dotenv` dependency changed from `>=0.2.0` to an exact pin `==1.0.1` in `pyproject.toml` ([commit 5f63873d](https://github.com/BerriAI/litellm/commit/5f63873dcad12d0aee51eabc974273eda5278205)). This makes litellm uninstallable alongside any library that requires `python-dotenv>=1.1.0` (e.g. `fastmcp[tasks]==3.2.0`).

Exact pins in published package metadata propagate to every consumer's resolver — reproducible Docker builds should use a lockfile instead.

### Steps to Reproduce

1. `uv add litellm==1.83.3 "fastmcp[tasks]==3.2.0"` 2. Resolution fails immediately

### Relevant log output

```shell × No solution found when resolving dependencies: ╰─▶ Because fastmcp==3.2.0 depends on python-dotenv>=1.1.0 and litellm==1.83.3 depends on python-dotenv==1.0.1, we can conclude that litellm==1.83.3 and fastmcp[tasks]==3.2.0 are incompatible. ```

### What part of LiteLLM is this about?

SDK (litellm Python package)

### What LiteLLM version are you on ?

1.83.1, 1.83.2, 1.83.3

### Twitter / LinkedIn details

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d19h2m59s ago — entered · #import:https:::github.com:berriai:litellm post #1830
Issue 32308 requires coordinated changes across routing, affinity, retry, and fallback behavior, with substantial regression testing for interacting policies. Issue 25210 is a narrowly scoped package-metadata correction.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search