-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django 3 End-of-life #262907
Comments
I did some testing of Mailman with Django 4 last week, and it seems fine, but I want to do a little more testing. |
This reverts commit 84f6a67. Mailman now supports Django 4.x. Link: NixOS#262907
Related to NixOS#262907 (Django3 removal from nixpkgs). This package already required an unreasonable amount of maintenance regularly for a such small leaf-package. It has a few highly outdated dependencies (e.g. flask 1, jinja2 2.11, sqlalchemy 1.3). After at least each Python package-set update one had to fix up a lot of dependencies to fix the package itself, so it was only useful on stable branches. And having so much outdated software in a security-sensitive piece of software seems questionable. Finally, globin and I won't be available for maintaining this now that Mayflower is migrating to another solution (and we'll do that as well) and I'd expect this to bitrot extremely quick if we both bail out.
End of life has been pushed back to the end of April 2024. My plan for 24.05 is to keep
Also we seem to have two new consumers, since this issue was opened.
|
Thanks for the heads up. Upstream has updated to django4 but also dropped support for postgresql, which is the only db supported by the module 🙃. I don't have much bandwidth and am not sure about the future course of action for seafile module. |
Should I wait for it to hit PyPi or change the source to the GitHub? |
If you think it is too early we might have to live with transitive |
Upstream says those CVEs aren't in their code path, and the package is unlikely security critical enough for us to chase pre releases, so I'll just leave it as is until pypi is updated. |
Django 3 was supported until 2024-04-01, and we're taking it into NixOS 24.05 under the condition of people having to opt into its consumption. Related: NixOS#262907
Will be marked vulnerable as of #313501, which will land in NixOS 24.05. |
For Baserow, it uses Django 4 in releases 1.22.2 and later, 4.1 in 1.22.3 and later. There's a lot of breaking changes between the currently packaged release(1.12.1) and these versions, so if upgraded, it should be mentioned in the release notes. For Etebase, there was an issue opened at etesync/server#173, but there's been no comments or seemingly any movement on it since March. |
archivebox has updated to Django 4 https://github.com/ArchiveBox/ArchiveBox/blob/99b19e19173296058bbc0d00cbcdc9f9632c7953/pyproject.toml |
@pyrox0: Done. Apologies for the delay! |
Thank you very much, appreciate the quick response on this! I'll see about getting the package bumped ASAP. Edit: See #316984. |
Removes the dependency on Django 3, fixing NixOS#262907.
Seahub can be checked off the list: #318727 |
One year later and I want to yank django 3.x from nixpkgs until the end of the year. |
Hi everyone, Django package maintainer here 👋
With Django 3.2.x running out of support after 2024/04/01 we have to make a decision how to handle it in NixOS 23.11.
https://endoflife.date/django
My preference would be to remove it before branch-off, but I fully expect you have packages that still require it. For now, I want you to check with your upstreams if and how their Django 4 migration is going, so we can make an informed decision.
The text was updated successfully, but these errors were encountered: