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
If TensorFlow make use of NumPy's C API (and produces wheels that use it), having a release of TensorFlow with wheels built against NumPy 2.0.0rc1 would be helpful to ensure NumPy 1 & 2 compatible wheels (as wheels built against NumPy 1 won't be compatible with NumPy 2). More details in this NumPy 2 ABI doc
Also would recommend incorporating NumPy 2 in TensorFlow's CI
Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share TensorFlow's current support status in issue (with any plans): numpy/numpy#26191
Lastly was unable to find an existing issue by searching or asking AI. So went ahead and opened this. If there's an existing one, happy to close and follow that
Problem description
NumPy 2.0 is coming out soon ( numpy/numpy#24300 ). NumPy 2.0.0rc1 packages for conda & wheels came out a month ago ( numpy/numpy#24300 (comment) )
Feature description
NumPy has put out a migration guide. More details are in the release notes
If TensorFlow make use of NumPy's C API (and produces wheels that use it), having a release of TensorFlow with wheels built against NumPy 2.0.0rc1 would be helpful to ensure NumPy 1 & 2 compatible wheels (as wheels built against NumPy 1 won't be compatible with NumPy 2). More details in this NumPy 2 ABI doc
Also would recommend incorporating NumPy 2 in TensorFlow's CI
Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share TensorFlow's current support status in issue (with any plans): numpy/numpy#26191
Additional information
There has been some discussion about TensorFlow's NumPy 2 plans here: numpy/numpy#26191 (comment)
Also the Keras team is interested in this question as they depend on TensorFlow: keras-team/keras#19691 (comment)
Lastly was unable to find an existing issue by searching or asking AI. So went ahead and opened this. If there's an existing one, happy to close and follow that
cc @MichaelHudgins @jakevdp @rgommers (for vis)
The text was updated successfully, but these errors were encountered: