Avoid potential test pipeline breakage in near future #2653
Conversation
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
- The new pip (25.3) is available now. It fully removes support for no-use-pep517, but nano arrow build replies on it. So for now we can pin the pip version to <25.3 - File a separate ticket to find a long-term solution to make nano arrow build compatible with pep 517 (not just test build, but also production build)
sfc-gh-turbaszek
added
DO_NOT_PORT_CHANGES_TO_SP
NO-CHANGELOG-UPDATES
sfc-gh-aling
approved these changes
Dec 3, 2025
sfc-gh-turbaszek
approved these changes
Dec 3, 2025
sfc-gh-turbaszek
deleted the
zyao-avoid-new-pip-affect-test-build-script-to-
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
--no-use-pep517, but nano arrow build replies on it. So for now we can pin the pip version to <25.3Please answer these questions before submitting your pull requests. Thanks!
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #NNNN
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Please write a short description of how your code change solves the related issue.
(Optional) PR for stored-proc connector: