BF: fix doctest failure with pre-release numpy #582
Merged
Conversation
This file contains hidden or 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
Numpy output printing has changed in upcoming 1.14 - trigger legacy printing for doctests.
|
That wasn't the case before, but things may have changed, for all I know. Testing this locally. |
|
The issues in Travis seem to have been pip-related, which have resolved themselves. This works on my end, too. The AppVeyor issue seems entirely unrelated. Merging. |
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.
Numpy output printing has changed in upcoming 1.14 - trigger legacy
printing for doctests.
Chris - I had to do
from nibabel.testing import setup_test as setup_moduletomake this work. Is this also true for the other imports of this function?