Drop Py3.6 support per NEP 29 #4469
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
jarrodmillman
force-pushed
the
drop-36-per-nep29
branch
from
9e607ba
to
f748f43
Compare
MridulS
pushed a commit
to MridulS/networkx
that referenced
this pull request
Feb 4, 2023
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.
Several of the core packages have decided to drop support for Python 3.6 on their next release.
scikit-image already has a release without Python 3.6 support:
NumPy, SciPy, and Pandas already have release candidates without Python 3.6 support:
I am not sure when Matplotlib is planning to make a new release, but they've removed support for 3.6 from master already.
GH actions/setup-python now supports PyPy-3.7:
I recommend we also follow NEP 29 and drop 3.6 support (which is what this PR does).
For more information see: