This repository has been archived by the owner on Nov 7, 2019. It is now read-only.
Update to Django 2.2 LTS #736
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
rmader
force-pushed
the
rm-2019-05-update-django-2.2
branch
from
05a60dd
to
ae69801
Compare
rmader
force-pushed
the
rm-2019-05-update-django-2.2
branch
from
ae69801
to
52711b8
Compare
rmader
force-pushed
the
rm-2019-05-update-django-2.2
branch
6 times, most recently
from
21b4bae
to
ef055f1
Compare
|
Boaaah now just working around sqlite bugs. |
rmader
force-pushed
the
rm-2019-05-update-django-2.2
branch
7 times, most recently
from
60d62a2
to
fae36e0
Compare
rmader
force-pushed
the
rm-2019-05-update-django-2.2
branch
from
fae36e0
to
77d2ce0
Compare
|
Alright, ready for review 🎉 |
MagdaN
approved these changes
Jul 11, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There's an issue around partners and the code involved looks like a bit of magic. Before we invest more into fixing that we should check if we don't dodge the partners altogether.Note: the migrations might fail on first try. This seems to be a bug in djangos migration system.