Fixing the test build #338
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
|
@syrusakbary Our test suites for 2.7 are failing across several outstanding PRs. #336 is going to get us Django 2.0 supported in full, but it's waiting on an upstream push to pytest. For now, we can get existing PRs fixed back up with just this change. |
Merged
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.
Several PRs are failing for unrelated reasons. Figuring out those reasons and getting the build passing again...
It looks like there is just one issue:
Django 2.0 is released and we aren't ready for that yet. #336 will fix it completely, but for now, we just need to not install 2.0 on python 2.7