Upgrade Django and other deps #21
Merged
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
cvitan
force-pushed
the
cvitan/django-upgrade
branch
from
f64d67a to
d4c29a1
Compare
cvitan
changed the title
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.
This upgrades Django to the oldest supported version, 1.11.27. As this is a major upgrade, it has the following known implications.
Breaking change
- The jsonfield library is replaced with the native
Django.contrib.postgres.fields.JSONField- this unfortunately makes it necessary to rebuild the database from scratch. There are ways around this, source but due to time constraints it's not part of this PR. Since the only field uses is not that major, it should be possible to at least recreate the fields without having to rebuild the entire DB for existing installations.Changes
--fake-initialflag.