Note that NumPy 2.0.0rc1 has been released on PyPI and is guaranteed to be ABI stable for the purpose of wheel building. Wheels built against NumPy 2.0.0rc1 should be backwards compatible to at least NumPy 1.22.4. There's a tracking table of major ecosystem projects that have 2.0-compliant/built wheels here: https://github.com/numpy/numpy/issues/26191
We can't do a release that is 2.0.0 compatible until pandas does I don't think, but I think they will do one early-mid next week based on feedback at the NASA ROSES call yesterday.
We'll have to check our testsuite situation against NumPy 2.0.0rc1 and the other NumPy-leveraging deps we use once they are available, but I don't anticipate any major issues. It will eventually be worth doing such a release for us because the of the strong backwards compatibility guarantees we get alongside NumPy 2.x support.
Note that NumPy
2.0.0rc1has been released on PyPI and is guaranteed to be ABI stable for the purpose of wheel building. Wheels built against NumPy2.0.0rc1should be backwards compatible to at least NumPy1.22.4. There's a tracking table of major ecosystem projects that have 2.0-compliant/built wheels here: https://github.com/numpy/numpy/issues/26191We can't do a release that is
2.0.0compatible untilpandasdoes I don't think, but I think they will do one early-mid next week based on feedback at the NASA ROSES call yesterday.We'll have to check our testsuite situation against NumPy
2.0.0rc1and the other NumPy-leveraging deps we use once they are available, but I don't anticipate any major issues. It will eventually be worth doing such a release for us because the of the strong backwards compatibility guarantees we get alongside NumPy 2.x support.