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 Keras against NumPy 2 in CI
Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share Keras'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 Keras doesn't have C/C++ usage of NumPy, only the Python changes would be relevant
The text was updated successfully, but these errors were encountered:
A relatively complete list of projects is in the table in the OP of issue: numpy/numpy#26191
With JAX, it sounds like they already have NumPy 2 support as of JAX 0.4.26: google/jax#19246
It sounds like TensorFlow is planning a release by end of May ( numpy/numpy#26191 (comment) ). Though we are waiting on more info from them as to whether NumPy 2 would make that release, but haven't heard back. So have gone ahead and raised a TensorFlow issue: tensorflow/tensorflow#67291
I have taken a quick look and things are looking good so far, but in order to run the full suite of unit tests we need to have a compatible TF build available. We'll have to wait on the np 2 compatible TF RC in order to do that.
Problem description
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) )
Feature description
To prepare for NumPy 2.0, it might be worthwhile to start testing Keras against NumPy 2 in CI
Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share Keras'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 Keras doesn't have C/C++ usage of NumPy, only the Python changes would be relevant
The text was updated successfully, but these errors were encountered: