Skip to content

Conversation

@aslonnie
Copy link
Collaborator

fixes min setup build

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
"${python}" -m pip install --upgrade pip
# 25.3 has breaking change where other Python packages like "click" does not work
# with it anymore. pip-compile will fail to work with the package's setup code.
"${python}" -m pip install pip==25.2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Pip Upgrade Command Missing --upgrade Flag

The pip install pip==25.2 command is missing the --upgrade flag, which prevents older pip versions from being upgraded to 25.2.

Fix in Cursor Fix in Web

@aslonnie aslonnie added the go add ONLY when ready to merge, run all tests label Oct 27, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request pins the pip version to 25.2 to fix a build failure caused by a breaking change in a newer version. The change is straightforward and should resolve the issue. My review includes a suggestion to improve the comment for better clarity and long-term maintainability by adding a TODO and generalizing the explanation to avoid potential confusion with the unconventional version numbers used.

Comment on lines +136 to +138
# 25.3 has breaking change where other Python packages like "click" does not work
# with it anymore. pip-compile will fail to work with the package's setup code.
"${python}" -m pip install pip==25.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Pinning pip is a good immediate fix for the build issue. For better long-term maintainability and clarity, I have a couple of suggestions.

First, the version numbers 25.3 and 25.2 are unconventional for pip, which usually follows a YY.N format (e.g., 24.1). This can be confusing for future maintainers.

Second, it's a good practice to add a TODO to track temporary fixes like this, making it easier to unpin the version once the upstream issue is resolved.

Here's a suggested change that incorporates these points by making the comment more general and adding a TODO:

Suggested change
# 25.3 has breaking change where other Python packages like "click" does not work
# with it anymore. pip-compile will fail to work with the package's setup code.
"${python}" -m pip install pip==25.2
# TODO(ci): Unpin pip once the upstream breaking change is fixed. See [link to issue if available].
# A recent pip version introduced a breaking change that affects packages like "click"
# and causes pip-compile to fail. Pinning to a known-good version as a workaround.
"${python}" -m pip install pip==25.2

@ray-gardener ray-gardener bot added the devprod label Oct 27, 2025
@aslonnie aslonnie merged commit f67f126 into master Oct 27, 2025
5 of 6 checks passed
@aslonnie aslonnie deleted the lonnie-251027-minsetupfix branch October 27, 2025 19:13
@aslonnie aslonnie mentioned this pull request Oct 30, 2025
aslonnie added a commit that referenced this pull request Oct 30, 2025
lint on code format and cherrypick #58215

---------

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
landscapepainter pushed a commit to landscapepainter/ray that referenced this pull request Nov 17, 2025
fixes min setup build

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
Aydin-ab pushed a commit to Aydin-ab/ray-aydin that referenced this pull request Nov 19, 2025
fixes min setup build

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devprod go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants