Drop support for Django 4.1 #1068
Conversation
francoisfreitag
force-pushed
the
dj41-rm
branch
3 times, most recently
from
54007c9
to
642a48c
Compare
docs/changelog.rst
Outdated
| @@ -19,6 +19,7 @@ ChangeLog | |||
| *Removed:* | |||
|
|
|||
| - Drop support for Django 4.0 | |||
| - Drop support for Django 4.1 | |||
There was a problem hiding this comment.
I'd rephrase this as "Stop testing for Django 4.1 compatibility".
We're not actively dropping that support.
There was a problem hiding this comment.
We’re removing the PyPI marker and no longer care for compatibility with Django 4.1, so I think drop support is accurate, although we’re not removing django 4.1 specific code?
There was a problem hiding this comment.
Well, when I read the changelog of a third-party package and see there "Drop support for Python 2", I understand that the code is likely to break with Python 2, for instance :)
There was a problem hiding this comment.
Code could break for Django 4.1 and we wouldn’t know, or care. But enough discussion on this topic, I updated to a more precise phrasing.
There was a problem hiding this comment.
When I see the "Drop support for X" in other projects I tend to view it as "use at your own risk", it may or may not work... Just my $0.02.
What you've got is fine too.
francoisfreitag
force-pushed
the
dj41-rm
branch
from
642a48c
to
2c00c39
Compare
Upstream dropped support in January 2024.
No description provided.