Remove support for Python 3.6 #500
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brettcannon
approved these changes
Jan 19, 2022
|
Any reason not to merge this, @pradyunsg , from a pip perspective? |
|
We already dropped support for 3.6 on pip's main branch. |
1 task
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the comment in #383 (comment), it seems that packaging will eventually drop support for Python 3.6, after the EoS.
Whenever the maintainers decide it is the right moment, I hope this PR helps 馃槃 (it is very trivial, but maybe it helps to make the work as easy as to press some buttons).
I went through the files checking that there was no conditional import and I also run pyugrade to double check something was missing.