Remove Python 3.6 legacy status #126
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
mauritsvanrees
approved these changes
Nov 2, 2021
icemac
approved these changes
Nov 3, 2021
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.
This change removes the part of cf84a7f that moved Python 3.6 to legacy status.
Please see the discussion at zopefoundation/Zope#988 (comment) for why I think it is a bad idea to be aggressive about retiring Python versions.
There's a more general issue here about how this package distinguishes Python versions. I think the distinctions are becoming more of an obstacle for real-life packages which lose Python version support for no good reason, just because a decision was made in this particular package.
Instead of generally thinking about which Python versions are at or near EOL (as this package does) we should think in terms of what our main packages like Zope or ZODB are still supporting. Those must keep good backwards compatibility in a given release series and can't just arbitrarily drop Python version support.