Drop Support for Python 3.5 and 3.6#3325
Merged
dlstadther merged 4 commits intospotify:masterfrom Dec 4, 2024
Merged
Conversation
Collaborator
Author
|
@RRap0so , branch protection rules will need to be adjusted again to handle the 3.6 tests i've removed within this PR. |
RRap0so
approved these changes
Dec 4, 2024
Contributor
|
@dlstadther done. |
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
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.
Description
Dropping support for Python 3.5 and 3.6
Motivation and Context
These Python versions have been End-of-Life status since 2021-12-23 or before.
Removing support for <3.7 will allow PRs (such as #3267) to make their necessary changes.
Have you tested this? If so, how?
CI