-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Update Django] Django 5.1 #5288
Comments
django-storages 1.14.4 should be good according to jschneier/django-storages#1444 |
@browniebroke you did some upstream work on DRF on this topic. Is it compatible with Django 5.1 or do we need to await a release? |
I did add it to the CI and everything passes without any changes. At work, we've got our main project running Django 5.1 and DRF 3.15 and didn't notice any issues. The only known incompatibility is that the current DRF 3.15 doesn't support |
@browniebroke I found an issue while running CI from Django 5.0.9 to 5.1.2. If a project is generated with option
This is caused by multiples changes in Django 5.1: django/django#16942 This change introduces a new field named The new default value of django/django/blob/263f7319192b217c4e3b1eea0ea7809836392bbc/django/contrib/auth/admin.py When cookiecutter-django/{{cookiecutter.project_slug}}/{{cookiecutter.project_slug}}/users/admin.py Lines 46 to 57 in 931e300
In Django documentation gives a possible solution: replace |
Yes we may have to adapt a few things, and thanks for sharing that, will be useful when we get to it. |
djangorestframework 3.15.1 supports Django 5.1 |
5.1 requirements tables
base.txt
local.txt
production.txt
The text was updated successfully, but these errors were encountered: