-
Notifications
You must be signed in to change notification settings - Fork 168
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
Upgrade to Django 4.2 #276
Comments
Instead of django 4+, maybe we should upgrade to 3.2. This is because django 3.2 will keep being supported even after django 4.0 and django 4.1 stops getting support. Here is a detailed description of that in graph https://www.djangoproject.com/download/ |
Hello @tuxology can I be assigned to this issue? |
@tuxology Please let me know if this is a priority |
@tuxology I think it's time we upgrade our django version. I think we've had issues in the past with this because of our custom summernote hack and the fact that it doesn't work well with higher django and jquery versions. |
we can proceed with this when #944 is merged |
There are many dependencies using APIs which seem to have been deprecated. Tried upgrading this over the holidays, but it seems there are issues. here are the previous reverts: #275
The text was updated successfully, but these errors were encountered: