-
-
Notifications
You must be signed in to change notification settings - Fork 765
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
Bump to Dj 4.x #6173
Bump to Dj 4.x #6173
Conversation
Only 1 error now |
IMO the flag for the custom manger support is just not present on django-mptt. Adding it adds a bunch of migrations so I did not commit that. |
We should look seriously into squashing migrations before a certain date, back a few major releases. |
@SchrodingersGat I think we should do stuff like that with the 1.0. Maybe make a 0.99 release before and add a check that everything was updated to that and have some breaking changes in the transition to 1.0 like removing old migrations, moving config files out of the code source, move plugins dir etc. |
FYI Debian 11 (Python 3.9, current min) is EOL 2024-08-15 so I think after that we could switch to Python 3.11 (default for Debian 12) or at least Python 3.10 (default for Ubuntu 22.04 which was released April 2022) |
@matmair happy with that. At some point we need to consider supporting python 3.12 - but that has only just been supported officially by django |
not reproducible on my machine
not reproducible on my machine
@SchrodingersGat can you check the TZ addition in the notification age? Seems to work for me but want to be sure. Should be ready for review otherwise. |
@matmair LGTM - glad that we finally got this one worked out :) |
I was getting nervous about the End of Life approaching; 0.14 is shaping up to be a good release. |
I've actually put a release data against |
Note (#6453) that this PR requires some changes to the setup configuration if running behind a proxy |
Close #2853
Follow up to #4584; Switch the code base to Django 4.2 (LTS) as 3.x is EOL in 2 months.