This repository has been archived by the owner on Feb 7, 2019. It is now read-only.
Django1.9, 1.10 and 1.11 compatibility #140
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
…bility hacks; Most tests passing again
…bility Conflicts: .travis.yml tox.ini versions/models.py
… code property...
… compatibility (in case someone started his project on a pre-1.8.3 Django version)
…ntermediary models, allowing for M2M migrations
…gration-time warnings
…ed as it is dropped in Django 1.11
…ngo110-compatibility
added 16 commits
September 10, 2017 18:57
… reference field (this was adapted in a previous commit today)
…y combination is run anyways
This was referenced Sep 11, 2017
Merged
Closed
This was referenced Sep 18, 2017
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.
This PR adds compatibility for Django 1.9 and up.
It includes fixes for "recent" issues like #129.
Since this PR breaks backward compatibility (w/ Django 1.8 and prior), I suggest to increase the major version number.
Also, I suggest to re-label the DJANGO_1.9 branch with "master", since we'll probably work on this code base in the future.