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 support #1324

Closed
jakirkham opened this issue Apr 24, 2024 · 2 comments · Fixed by #1332
Closed

NumPy 2.0 support #1324

jakirkham opened this issue Apr 24, 2024 · 2 comments · Fixed by #1332

Comments

@jakirkham
Copy link

Is your feature request related to a problem? Please describe.

NumPy 2.0 is coming out soon ( numpy/numpy#24300 ). NumPy 2.0.0rc1 packages for conda & wheels came out 3 weeks back ( numpy/numpy#24300 (comment) )

Describe the solution you'd like

To prepare for NumPy 2.0, it might be worthwhile to start testing Datashader against NumPy 2 in CI

Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share Datashader's current support status in issue (with any plans): numpy/numpy#26191

NumPy has put out a migration guide. More details are in the release notes. As Datashader doesn't have C/C++ usage of NumPy, only the Python changes would be relevant

Describe alternatives you've considered

In the short term, Datashader may wish to set an upper bound on NumPy version until testing can happen. Alternatively Datashader could wait for user issues and address as those come up

Maybe there are other options that haven't been considered here

Additional context

NA

@hoxbro
Copy link
Member

hoxbro commented Apr 25, 2024

As we also depend heavily on numba, there is really no way for us to test without the 0.60.0 release.

We have updated the codebase in #1289 and #1306.

@jakirkham
Copy link
Author

There is now a Numba 0.60.0rc1 available for testing 🙂

xref: numba/numba#9544 (comment)

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 a pull request may close this issue.

2 participants