-
Notifications
You must be signed in to change notification settings - Fork 2
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
deps: remove upper numpy bound #146
Conversation
Seems we need to release scippneutron and depend on the latest version here before this can be merged. |
I released ScippNexus 24.06.0 with the fix. |
pyproject.toml
Outdated
"scippnexus>=23.12.1", # 23.12.0 and below deadlock in threaded use | ||
"scippnexus>=24.6.0", # Below 24.6.0 incompatible with Numpy 2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since ESSsans does not require Numpy 2 we should not have such a lower bound, I think? That is, put back 23.12.1.
requirements/base.in
Outdated
@@ -12,4 +12,4 @@ pythreejs | |||
sciline>=24.06.0 | |||
scipp>=23.8.0 | |||
scippneutron>=23.9.0 | |||
scippnexus>=23.12.1 | |||
scippnexus>=24.6.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since ScippNexus works also with lower versions, I also do not see a reason for the lower bound here. Revert to 23.12.1 and let pip-compile-multi
deal with the rest?
93d93f3
to
77e8c94
Compare
Waiting for scipp/plopp#351 |
77e8c94
to
9da385a
Compare
9da385a
to
2486e36
Compare
Now that scipp/scippnexus#215 is closed the upper bound on
numpy
can be removed.Or, can it? We'll see what the ci says.