Drop support for DRF 3.14 and Django 5.0 #384
Open
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
@alanjds says > I say that because _usually_ I like to keep support at least for the latest-1 version of stuff. which would make 3.14 a target to drop
it's EOL since August 2024
|
This builds on #383 which should probably be merged first |
|
In cd53288 there was already a not-reverted removal of 3.14 from requirements.txt, which may or may not imply that 3.14 support was already dropped. (other 3.14 removals were later reverted) |
|
I understand that there are no more support for DRF 3.14 & Django 5.0, but idk if we want to remove them from CI. Python EOLed versions, sure, always. That said, I will keep the PR open, so we can easily apply it in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
No description provided.