-
Notifications
You must be signed in to change notification settings - Fork 533
CI: Test against minimum versions #2576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
64a027c
to
22374ae
Compare
Codecov Report
@@ Coverage Diff @@
## master #2576 +/- ##
=========================================
+ Coverage 67.57% 67.6% +0.02%
=========================================
Files 333 333
Lines 42547 42550 +3
Branches 5266 5267 +1
=========================================
+ Hits 28750 28764 +14
+ Misses 13124 13113 -11
Partials 673 673
Continue to review full report at Codecov.
|
Looks like we're running up against issues when numpy==1.9 and scipy is 0.14.0, 0.16.0 or 0.18.1. Python < 3.6, scipy == {0.14.0, 0.16.0}
Python == 3.6, scipy == 0.18.1
|
@effigies - do we know what the python/numpy/scipy version compatibility matrix looks like? my simple searches did not turn up anything concrete. |
I do not. I picked the scipy minimum versions based on which ones had wheels on PyPI. Judging by the current |
While I think it's a good goal to test against minimum versions, I don't think I'm going to have the time to track this one down. |
@satra I added this issue to regtest to not forget |
We're currently testing against the most recent versions of our dependencies, which makes it harder to identify when we accidentally depend on newer features. See, e.g., #2181.