-
Notifications
You must be signed in to change notification settings - Fork 5
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
[PROD] Django upgrade to 4.2 #1990
Comments
Useful source: https://www.freecodecamp.org/news/importerror-cannot-import-name-force-text-from-django-utils-encoding-python-error-solved/ |
|
|
On developer side this change will require a database reload, due to we must shift to Postgresql 12.
Then the load to the new db can be done via a simple
|
Issue
According to https://endoflife.date/django the end of support of the recent 3.2 Django LTS version is in April 2024.
So (if possible, in March) we should upgrade to Django 4.2 LTS.
@batpad @thenav56 @k9845
The text was updated successfully, but these errors were encountered: