Restore compatibility with pytest #921
Merged
+7
−6
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
|
Tests now fail because we pinned |
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.
pytest has deprecated using a
[pytest]section insetup.cfg; it only supports[tool:pytest]now. This causes Travis builds to fail. We could either fix pytest to an old version inrequirements-dev.txt, or fixsetup.cfg-- this PR chooses the latter.Furthermore, the default format for printing floating point arrays has changed in numpy; there was an additional leading space in front of every number in earlier versions. This causes one of the doctests to fail. Again, we could either fix a particular numpy dependency or fix the doctest. This PR chooses the latter, setting the formatting options inside the doctest (the NORMALIZE_WHITESPACE flag is not enough because it does not cover the change from
[ 1.0to[1.0).