Skip to content

Conversation

@wchargin
Copy link
Contributor

Summary:
As of #4510, we don’t need six, so we can remove it from the Pip
package requirements.

Part of #4488.

Test Plan:
Running :extract_pip_package and installing it into a virtualenv still
installs six as a transitive dep, so this is actually no functional
change for now. Maybe one day.

wchargin-branch: py3-norequire-six

Summary:
As of #4510, we don’t need `six`, so we can remove it from the Pip
package requirements.

Part of #4488.

Test Plan:
Running `:extract_pip_package` and installing it into a virtualenv still
installs `six` as a transitive dep, so this is actually no functional
change for now. Maybe one day.

wchargin-branch: py3-norequire-six
wchargin-source: c7a05be7531841c2c998bf06ceb3501c2a80f16a
@wchargin
Copy link
Contributor Author

(Oops, forgot to request review.)

Copy link
Contributor

@nfelt nfelt left a comment

Choose a reason for hiding this comment

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

You could say six has been... deep-sixed 🥁

@wchargin wchargin merged commit 24b33a3 into master Jan 14, 2021
@wchargin wchargin deleted the wchargin-py3-norequire-six branch January 14, 2021 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants