Drop support for Django 4.2 and python 3.9#2220
Merged
carltongibson merged 2 commits intodjango:mainfrom Apr 22, 2026
Merged
Conversation
Member
|
Looks about right @p-r-a-v-i-n. Thanks. We probably need to remove Python 3.9 from the GHA workflows too. |
carltongibson
approved these changes
Apr 22, 2026
Member
carltongibson
left a comment
There was a problem hiding this comment.
Let's have it. Thanks @p-r-a-v-i-n 🎁
carltongibson
added a commit
that referenced
this pull request
Apr 22, 2026
Contributor
Author
|
Hey @carltongibson , For curiosity I wanna know why do we still support django 5.1 , and i have seen this not in also channel but in other django packages too. |
Member
|
@p-r-a-v-i-n — Yep, we can drop 5.1 too. Fancy doing that? |
Contributor
Author
yes |
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
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.
check here