WIP: Update to Django 5.1 #2264
Draft
+17
−14
Conversation
This file contains 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
|
The issue here is with coding systems test failures, due to the way the tests use databases. |
|
This also needs local testing as previously to ensure everything is OK with the upgrade. |
StevenMaude
added
the
deck-scrubbing
This changes `CheckConstraint.check` to `CheckConstraint.condition`. See also opensafely-core/job-server@190a645
StevenMaude
force-pushed
the
steve/django-5.1
branch
from
0c3126d to
bc9c47c
Compare
This results in a warning if not enabled, but will be the default behaviour in Django 6. Therefore, enable the setting and suppress the deprecation warning resulting from having that setting enabled (which will be removed in Django 6). See https://adamj.eu/tech/2023/12/07/django-fix-urlfield-assume-scheme-warnings/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2115.
This PR is to: