-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Install latest version of setuptools #7290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is 👍 . We may want to roll this out gradually, tho. This change will affect all the builds. Maybe adding a feature flag first, enable in some ~k projects and then remove the flag?
I don't know, feels safe to upgrade that package. @readthedocs/core thoughts on using a feature flag for a while? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm dismissing my own review here. I think the right path to move forward here is to add a feature flag with future_default_true=True
(#7524)
I think this is another "we need to figure out what to do with default versions" issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
2ba36a4
to
236bf6a
Compare
This is under a feature flag now |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me to use a feature flag for this.
cmd = pip_install_cmd + [pip_version, setuptools_version] | ||
self.build_env.run( | ||
*cmd, bin_path=self.venv_bin(), cwd=self.checkout_path | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are changing where we install setuptools
here.
Now we are installing it together with pip
as the first command we executed. Before, we were installing it together with our own dependencies. I don't think this is something bad, but definitely a change that may break in a random way 🙃
It makes sense to be installed with pip
to me; but we should keep an eye on this.
Closes #7241
We have experienced other issues in the past bc of using an outdated version of setuptools too