-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Upgrade application to Django 5.2 #12079
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
Comments
Here is how we did the upgrade for 4.2: #10595 |
I gave this a try but it seems we can't upgrade yet because Also, judging by the |
These are the new things I found interesting in 5.x that we may want to try it out:
|
It seems we are able to upgrade |
Upgrade our code base to Django 5.2 - `django-safemigrate` had to be upgraded: you will find _a lot of_ changes like `Safe.before_deploy` -> `Safe.before_deploy()` (all of them are in this particular commit: 4273e83) - I had to borrow `django.core.files.storage.get_storage_class` because it was deleted from Django 5.2 - `assertFormError` tests were updated to match the new signature - `django-celery-beat` and `django-storages` were upgraded - Update some old migrations referring to indexes to make them work Closes #12079 Closes #11505
* Upgrade django-upgrade to latest version and Django 5.2 Related readthedocs/readthedocs.org#12079 * Version fix * Fix addons PATHs on Docker Compose * Upgrade all pre-commit hooks
I'm reopening it because we had to downgrade it again due to |
5.2 is out: https://docs.djangoproject.com/es/5.2/releases/5.2/
We want to plan and upgrade to the latest version.
There is a django upgrade script we have used already some time ago.
The text was updated successfully, but these errors were encountered: