-
Notifications
You must be signed in to change notification settings - Fork 65
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
Build with NumPy 1.17 #148
Conversation
Instead of letting `host`'s `numpy` have a minimum, which could float to a high version that is in turn pinned to a high version in `run`, build using the minimum required `numpy` version. That way the minimum is set similarly in `host` and a wide range of `numpy`'s will still work at runtime.
In particular this caused some issues when installing |
Seems to be overly strict from a solver perspective.
rerun tests (one of the jobs failed, but it looks unrelated) |
rerun tests (pending job was likely lost during rename) |
@gpucibot merge |
rerun tests |
Debugging in PR ( #153 ) |
the segfault failure in this PR is unrelated to the |
Instead of letting
host
'snumpy
have a minimum, which could float to a high version that is in turn pinned to a high version inrun
, build using the minimum requirednumpy
version. That way the minimum is set similarly inhost
and a wide range ofnumpy
's will still work at runtime.cc @quasiben (for awareness)