-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 minimal Django to 4.2 #8637
Conversation
Not for now – increasing minimal Django version above 4.0 means dropping support for Python 3.7 what is currently not possible for us. But we should really get rid of Python 3.7 on our production servers. |
This pull request has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Let's do this for the 4.17 release. |
This comment was marked as outdated.
This comment was marked as outdated.
8da64f6
to
b05f390
Compare
This is deprecated in Django 4.2.
35d05b8
to
730ecc7
Compare
- This is current LTS release. - Needed for RenameIndex operation in the migrations. - Adjusted migrations CI to use older Python for older version. - Bump miminal Python, PostgreSQL, MySQL and MariaDB versions.
Proposed changes
This is deprecated in Django 4.2. See https://docs.djangoproject.com/en/dev/releases/4.2/#features-deprecated-in-4-2
Checklist
Other information