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 5.0 compatibility #9964
Comments
The issue with MySQL seems to affect Django 4.2, too. Haven't checked which commit in Django caused this issue, but the migration that triggers the crash is This can be replicated through the following steps:
Log
|
Found it, regression is in django/django@b731e88 introduced in django/django#15254. |
Upstream ticket created: https://code.djangoproject.com/ticket/34304 |
PR opened on upstream: django/django#16509 |
Upstream PR has been merged, #9974 is now passing. |
Issue Summary
Django 4.2 alpha 1 was released last week, which means that Django's
main
branch is now on 5.0.Currently, our
main
branch tests are failing against Django'smain
branch. This issue serves as a tracker of any issues with our code that make it incompatible with Django 5.0.django.utils.timezone.utc
has been removed. It is an alias todatetime.timezone.utc
and we should usedatetime.timezone.utc
directly. Might need to check if there's any difference topytz.utc
, as that seems to be what Django used in earlier versions.assertFormError
andassertFormsetError
no longer allows passing response and form context nameQuerySet.iterator()
on a queryset that prefetches related objects without providing thechunk_size
argument is no longer allowed.django.contrib.auth.views.LogoutView
anddjango.contrib.auth.views.logout_then_login()
is removed.Blocked by wagtail/django-modelcluster#169.
Will update if I find more.
The text was updated successfully, but these errors were encountered: