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
Install six as core requirement for builds #7710
Conversation
fb764ca
to
6151333
Compare
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.
6151333
to
7a9e935
Compare
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 |
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.
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.
Our config file depends on
six
package to checkstring_types
, so we need tomake sure we have it installed as a core requirement.
We were pinning
sphinx<2
which depends onsix
. Now, all the projects usingUSE_LATEST_SPHINX
will install justsphinx
(currently 3.3.1) which does notdepends on
six
anymore and all they builds will fail.Closes #7705