Provide support for Django 2.0+ #4
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
amir-qayyum-khan
force-pushed
the
fix_aq_django_2
branch
2 times, most recently
from
bc578f0 to
56d4cdf
Compare
mbertrand
requested changes
Jul 17, 2018
amir-qayyum-khan
force-pushed
the
fix_aq_django_2
branch
from
35c3fc6 to
68c3e95
Compare
|
Done @mbertrand |
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.
What are the relevant tickets?
fixes #3
What's this PR do?
It fix
ForeignKeywhich requires 2 parameter from Django 2.0. But before that only one param was mandatoryHow should this be manually tested?
Run migration with Django 2.0
@pdpinch
Note: open it upsteam