v1.2.0 prep for Django 1.5 compatibility #11
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
…ture Armstrong.Dev
…m future` to make this change work in Django 1.3+.
…tructions, add missing install instruction
…ck for 1.3. Fixes deprecation warning.
Closed
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.
TravisCI will probably have a hard time with this (or it may produce inaccurate results) because the other required Armstrong packages (AppContent, CoreContent, Sections and Access) all still have pinned Django versions.Nope it works. TravisCI installs the proper version after all the package requirements, so while Django is installed twice, the last one is the version we want tested. (this is part of why the 1.3 and 1.5 tests take so long)fab testrun locally works against the three Django versions.