You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as i was looking at the failure messages on travis tests, I realize that none of the tests for testing different versions of numpy actually uses the version in the config file.
for a similar reason, in the dithering branch and in my pull request, one of the tests is failing because numpy version 1.13 only works for Python version 2.7 or >= 3.4.
The text was updated successfully, but these errors were encountered:
@tolgayapici Can you give a bit more detail on the issue here? If I look at this recent travis log which is configured to use numpy 1.10, I see, for example:
$ export NUMPY_VERSION=1.10
...
The following NEW packages will be INSTALLED:
mkl: 11.3.3-0
numpy: 1.10.4-py35_2
...
Numpy: 1.10.4
...
It looks like the test is using the specified version.
We are currently testing numpy 1.10, 1.11, 1.12 and "prerelease". I agree this should be updated but that's a separate issue, so I am closing this now.
as i was looking at the failure messages on travis tests, I realize that none of the tests for testing different versions of numpy actually uses the version in the config file.
for a similar reason, in the dithering branch and in my pull request, one of the tests is failing because numpy version 1.13 only works for Python version 2.7 or >= 3.4.
The text was updated successfully, but these errors were encountered: