Pin pyarrow>=22.0.0 on Python 3.14 in constraints generation#65216
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 14, 2026
Merged
Pin pyarrow>=22.0.0 on Python 3.14 in constraints generation#65216potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-2-test
vatsrahul1001
approved these changes
Apr 14, 2026
sunank200
approved these changes
Apr 14, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Apr 14, 2026
…constraints (#65216) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Apr 14, 2026
…constraints (#65216) (#65219) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…constraints (#65216) (#65219) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…constraints (#65216) (#65219) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…constraints (#65216) (#65219) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…constraints (#65216) (#65219) Older pyarrow releases do not publish cp314 wheels on PyPI, so uv falls back to building pyarrow from source when resolving the highest versions of provider dependencies on Python 3.14 — which fails. pyarrow 22.0.0 is the first release shipping Python 3.14 wheels, so constrain it for that Python version when generating constraints. (cherry picked from commit cd28a00) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
3 participants
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.
When generating the highest-resolution constraints for provider dependencies on Python 3.14,
uvattempts to resolve olderpyarrowversions that do not shipcp314wheels on PyPI. It then falls back to buildingpyarrowfrom source, which fails in the constraints-generation environment.pyarrow 22.0.0is the first release that publishes Python 3.14 wheels, so this adds an additional constraintpyarrow>=22.0.0; python_version >= '3.14'to the highest-resolution constraints pin list used bygenerate_constraints_pypi_providers. The comment block above the pin is updated to document the current exclusion and the rationale.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.6 (1M context) following the guidelines