[WIP] Add support for django < 1.8 #161
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
rodxavier
changed the title
rodxavier
force-pushed
the
django18
branch
3 times, most recently
from
ddd5553
to
92e681e
Compare
|
Nice. I'll try to look at what's failing over the weekend, and try to get an idea of the impact on field type changes. It'll require a migration for anyone upgrading to Django 1.8. |
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.
Built upon @macro1's changes. The build's currently failing on a
OperationalError: no such tableerror. I'm not sure if it's some kind of a concurrency problem with sqlite or something else.