Drop Python 3.6 support #55
Merged
Conversation
This file contains hidden or 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
Member
Author
|
This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Fri 08 Oct 03:00 GMT (Thu 07 Oct 23:00 my local). |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Technically, we could drop this as of June 23, 2020, since we're following NEP 29 here. However, there was no need until I started working on #54, where I want defaults in a
namedtuple(introduced in Python 3.7).Not adding Python 3.10 to the test matrix yet because we're waiting on support from our requirements (which, y'know, starts with conda-forge having Python 3.10 available.)