litellm - 💡(How to fix) Fix Consider loosening constraints in pyproject.toml [1 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#26777Fetched 2026-04-30 06:20:04
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
1
Author
Participants
RAW_BUFFERClick to expand / collapse

From 1.83.0 to 1.83.1 the version constraints in pyproject.toml have gotten quite narrow. As of the current main branch this is still the case.

For example, pydantic changed from ^2.5.0 to 2.12.5. This means that litellm now dictates that people using it in their python apps or libraries cannot use pydantic 2.13.

I wonder why this change was made? And may I suggest loosening these contraints, e.g. specifying >=2.12.0 for pydantic?

If it is testing that you're worried about, you could consider running your tests with both uv sync (all latest versions) and uv sync --resolution=lowest (all "oldest" version) to cover a wide spectrum of versions.

extent analysis

TL;DR

Loosening version constraints in pyproject.toml, such as specifying >=2.12.0 for pydantic, may resolve the issue.

Guidance

  • Review the version constraints in pyproject.toml to identify overly restrictive dependencies, such as pydantic 2.12.5.
  • Consider loosening these constraints to allow for more flexibility, e.g., >=2.12.0 for pydantic.
  • To ensure compatibility, run tests with both the latest and oldest versions of dependencies using uv sync and uv sync --resolution=lowest.
  • Evaluate the trade-offs between strict version control and flexibility for users of the library.

Notes

The suggested change may introduce potential compatibility issues if not thoroughly tested. It is essential to weigh the benefits of loosened constraints against the potential risks.

Recommendation

Apply workaround: Loosen version constraints in pyproject.toml to allow for more flexibility, as this will enable users to utilize a broader range of dependency versions, including pydantic 2.13.

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 Consider loosening constraints in pyproject.toml [1 participants]