Skip to content

Install six as core requirement for builds #7710

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 1 commit into from
Dec 1, 2020
Merged

Conversation

humitos
Copy link
Member

@humitos humitos commented Nov 30, 2020

Our config file depends on six package to check string_types, so we need to
make sure we have it installed as a core requirement.

We were pinning sphinx<2 which depends on six. Now, all the projects using
USE_LATEST_SPHINX will install just sphinx (currently 3.3.1) which does not
depends on six anymore and all they builds will fail.

USE_LATEST_SPHINX is marked for all future projects. So, new projects are hitting this issue currently. I de-activate this feature for new projects while we solve and deploy this.

We could remove this dependency completely by copying the relevant lines from six, but I think it's safer to use six while we support Python 2 & 3 together. To remove it, we would need to confirm that we are not requiring six anywhere else as well.

Closes #7705

@humitos humitos requested a review from a team November 30, 2020 10:53
@humitos humitos force-pushed the humitos/install-six branch from fb764ca to 6151333 Compare November 30, 2020 11:04
Our config file depends on `six` package to check `string_types`, so we need to
make sure we have it installed as a core requirement.

We were pinning `sphinx<2` which depends on `six`. Now, all the projects using
`USE_LATEST_SPHINX` will install just `sphinx` (currently 3.3.1) which does not
depends on `six` anymore and all they builds will fail.
@humitos humitos force-pushed the humitos/install-six branch from 6151333 to 7a9e935 Compare November 30, 2020 11:15
@stsewd
Copy link
Member

stsewd commented Nov 30, 2020

I think this is a good opportunity to start getting rid of implicit dependencies, and just do the logic, seems small to replace.

https://github.com/benjaminp/six/blob/c0be8815d13df45b6ae471c4c436cce8c192245d/six.py#L36-L49

Copy link
Member

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

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

Agreed with @stsewd -- we should just fix our logic to not depend on six. If we can't update the PR to do that though, we should ship this PR this week, and add a TODO to change the logic.

@humitos humitos merged commit 475f12d into master Dec 1, 2020
@humitos humitos deleted the humitos/install-six branch December 1, 2020 14:32
stsewd added a commit that referenced this pull request Feb 2, 2021
Reverts #7710
@stsewd stsewd mentioned this pull request Feb 2, 2021
stsewd added a commit that referenced this pull request Feb 2, 2021
Reverts #7710
stsewd added a commit that referenced this pull request Feb 2, 2021
Reverts #7710
stsewd added a commit that referenced this pull request Feb 24, 2021
agjohnson pushed a commit that referenced this pull request Mar 2, 2021
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.

ModuleNotFoundError: No module named 'six' on build
3 participants