Add support for Python 3.6-3.9, drop EOL 2.6 and 3.2-3.4 #29
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
|
Passing CI build: Here's a build before the 3.9 fix, showing the problem: |
Diaoul
approved these changes
Jul 14, 2020
Closed
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.
Fixes #28.
This PR:
Declares support for and tests new Python 3.6-3.8.
It tests on Python 3.9-dev, due out in October, but already in alpha. It fixes a removed deprecation to use
collections.abcwhere available.This also drops support for EOL Python 2.6, 3.2-3.4.
Add
python_requiresmetadata to help pip install for people on older Python versions.I haven't removed EOL 2.7 yet, but would recommend doing so as well. Please let me know if you'd like that removing too, but I mainly recommend getting the 3.9 fix in as soon as possible.
Thank you!