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

Numpy >= 2.0 #584

Open
Lukas113 opened this issue Jun 28, 2024 · 3 comments
Open

Numpy >= 2.0 #584

Lukas113 opened this issue Jun 28, 2024 · 3 comments
Labels
bug Something isn't working prio-high High priority

Comments

@Lukas113
Copy link
Collaborator

Numpy release: https://numpy.org/news/#:~:text=16%20Jun%2C%202024%20%E2%80%93%20NumPy%202.0,the%20Python%20and%20C%20APIs.

This is an issue for us at the moment, because we're not compatible with it at the moment. At least, the underscore numpy-types have to be replaced with the according alias.

Currently, it's not considered as stable, but it will be soon.

@Lukas113 Lukas113 added bug Something isn't working prio-high High priority labels Jun 28, 2024
@Lukas113
Copy link
Collaborator Author

We would't have noticed sooned if we would use ruff. This would also replace any tool we now use for linting & formatting. However, this is probably worth another issue.

@Lukas113
Copy link
Collaborator Author

The minimum we should do is to make it numpy >= 2.0 compatible ASAP and hope that each dependency (direct and transversal) is also compatible. Otherwise, we would have to think about dependency-management again (either update or restrict deps).

@Lukas113
Copy link
Collaborator Author

Lukas113 commented Jul 19, 2024

The breaking changes I know atm:

  • typing np.float_, np.int_, etc ... will be removed. It's recommended to use np.float64, np.int64, etc ... instead

image

This also includes Karabo Feedstock builds & forked repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio-high High priority
Projects
None yet
Development

No branches or pull requests

1 participant