Skip to content

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

Merged
merged 7 commits into from
Jan 21, 2021
Merged

Install latest version of setuptools #7290

merged 7 commits into from
Jan 21, 2021

Conversation

stsewd
Copy link
Member

@stsewd stsewd commented Jul 13, 2020

Closes #7241

We have experienced other issues in the past bc of using an outdated version of setuptools too

humitos
humitos previously approved these changes Jul 14, 2020
Copy link
Member

@humitos humitos left a 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?

@stsewd
Copy link
Member Author

stsewd commented Jul 16, 2020

I don't know, feels safe to upgrade that package. @readthedocs/core thoughts on using a feature flag for a while?

@stale
Copy link

stale bot commented Oct 11, 2020

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Oct 11, 2020
@stsewd stsewd requested a review from a team October 12, 2020 14:53
@stsewd stsewd removed the Status: stale Issue will be considered inactive soon label Oct 12, 2020
@humitos humitos dismissed their stale review October 12, 2020 16:58

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)

@ericholscher
Copy link
Member

I think this is another "we need to figure out what to do with default versions" issue.

@stale
Copy link

stale bot commented Nov 26, 2020

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Nov 26, 2020
@stale stale bot removed the Status: stale Issue will be considered inactive soon label Nov 30, 2020
@stsewd stsewd force-pushed the use-latest-setuptools branch from 2ba36a4 to 236bf6a Compare November 30, 2020 18:47
@stsewd
Copy link
Member Author

stsewd commented Nov 30, 2020

This is under a feature flag now

@stsewd stsewd requested a review from humitos November 30, 2020 18:55
@stale
Copy link

stale bot commented Jan 17, 2021

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 17, 2021
@stsewd stsewd removed the Status: stale Issue will be considered inactive soon label Jan 18, 2021
Copy link
Member

@humitos humitos left a 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.

Comment on lines +353 to 356
cmd = pip_install_cmd + [pip_version, setuptools_version]
self.build_env.run(
*cmd, bin_path=self.venv_bin(), cwd=self.checkout_path
)
Copy link
Member

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.

@stsewd stsewd merged commit dee00ce into master Jan 21, 2021
@stsewd stsewd deleted the use-latest-setuptools branch January 21, 2021 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade setuptools versions before installation like we do with pip
3 participants