Restore the evaluation extra of google-cloud-aiplatform - #71520
Open
potiuk wants to merge 1 commit into
Open
Conversation
The extra was dropped and its contents inlined because it capped litellm below the versions carrying the Python 3.14 security fixes. google-cloud-aiplatform 1.164.0 lifts that cap, so the workaround has nothing left to work around, and carrying a copy of somebody else's extra only lets the two drift apart. The floor moves to 1.164.0 because every earlier release still ships the capped extra. Fixed upstream in: googleapis/python-aiplatform#7057
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts the workaround from #71273, which dropped the
evaluationextra ofgoogle-cloud-aiplatformand inlined its contents, because that extra cappedlitellm below the versions we need on Python 3.14.
google-cloud-aiplatform1.164.0 lifts the cap — itsevaluationextra nowasks for
litellm>=1.83.7,<1.86.0under 3.14 andlitellm>=1.93.0,<1.97.0from 3.14 on, which is what the inlined copy asked for. Verified on PyPI:
1.164.0 was published 2026-08-12 and its
requires_distcarries those twomarkers. The floor moves to 1.164.0 because every earlier release still ships
the capped extra.
The
uv.lockresolution is unchanged for litellm (1.85.7 under 3.14, 1.95.0from 3.14 on). scikit-learn on Python 3.10 goes back to 1.5.2, which is what
the upstream extra pins there (
scikit-learn<1.6.0; python_version<='3.10') —the
>=1.6.0floor existed only in the inlined copy.1.164.0 was published inside the rolling
exclude-newer = "4 days"window, soit needs a temporary per-package cutoff in the root
pyproject.toml, followingthe same pattern as the
pydantic-ai-skillsentry next to it. That entry can goonce the window advances past 2026-08-12.
Fixed upstream in: googleapis/python-aiplatform#7057
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines