Drop Python 3.8 as EOL #9635
Draft
Drop Python 3.8 as EOL #9635
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
|
we have to decide when we will drop python 3.8 |
|
@auvipy I'd prefer it if issues like this linked cleanly to Python's deprecation timelines. |
I agree that's an ideal place we should aim for. If I'm realistic, though, we're not there yet. I think we should release bug fixes more often (perhaps on a monthly basis?) and align our feature releases (3.x) to be close to Django's. Dropping EOL Python versions can be done as soon as possible to be released the next time we bump the minor version (assuming we'll never bump the major again). |
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.
After DRF 3.16 release is done, it might be right time to drop python 3.8 support... until then