Skip to content
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

Merged
merged 1 commit into from
Jun 18, 2024
Merged

deps: remove upper numpy bound #146

merged 1 commit into from
Jun 18, 2024

Conversation

jokasimr
Copy link
Contributor

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.

@jokasimr
Copy link
Contributor Author

Seems we need to release scippneutron and depend on the latest version here before this can be merged.

@SimonHeybrock
Copy link
Member

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
Copy link
Member

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.

@@ -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
Copy link
Member

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?

@jokasimr
Copy link
Contributor Author

Waiting for scipp/plopp#351

@jokasimr jokasimr enabled auto-merge (squash) June 18, 2024 12:49
@jokasimr jokasimr merged commit faa6419 into main Jun 18, 2024
3 checks passed
@jokasimr jokasimr deleted the remove-upper-snx branch June 18, 2024 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants