Updated to Django 3.2. #183
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmispelon
force-pushed
the
django-3.2
branch
4 times, most recently
from
b2f2905 to
c0e09e7
Compare
This was referenced Feb 18, 2024
This also fixes is_safe_url() deprecation warnings.
|
Rebased. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because we use so little of Django, I figured it was fine to make the jump all at once. I would still suggest merging #181 first, just for the extra piece of mind.
I activated
PYTHONWARNINGS=errorin CI and fixed the deprecation warnings that came up. This will make the future update to Django >= 4.0 easier (we'll have to work that one in parallel with django/djangoproject.com).Because we don't manage any db from Django there is no need for any operation after deploying this.