Drop Python 3.6, default to running on 3.10 #124
Draft
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
PeterJCLaw
force-pushed
the
drop-python-36
branch
from
f48aea2 to
8186c17
Compare
PeterJCLaw
force-pushed
the
drop-python-36
branch
from
8186c17 to
2a3d355
Compare
PeterJCLaw
force-pushed
the
newer-circle-image
branch
from
a1b114d to
c81f772
Compare
PeterJCLaw
force-pushed
the
drop-python-36
branch
from
2a3d355 to
b3595cd
Compare
Python 3.6 is well beyond end-of-life (December 2021). While 3.7 is still supported, it doesn't have long left (mid 2023). We should therefore still support using it, but there's no compelling reason to default to it.
PeterJCLaw
force-pushed
the
drop-python-36
branch
from
b3595cd to
3ecf593
Compare
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.
Python 3.6 is well beyond end-of-life (December 2021). While 3.7 is still supported, it doesn't have long left (mid 2023). We should therefore still support using it, but there's no compelling reason to default to it.