Adding support for Django 1.7 Migrations #25
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
2 similar comments
|
If you accept this, it might be worthwhile getting travis to build on Django 1.6 and 1.7; Coverage shouldn't decrease, then. |
|
Awesome, thanks. |
bogdal
added a commit
that referenced
this pull request
Apr 1, 2015
Adding support for Django 1.7 Migrations
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 adds support for the new migrations that appear in Django 1.7. The older, south migrations have been moved into a
south_migrationsdirectory, which according the docs is where south 1.0 will look for them.As long as users are using South 1.0, this change should work for Django 1.7 and (supported) earlier versions.