You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: