Numpy 2.0 compat plan #2353
Description
I read through #2345 (comment), numpy/numpy#24300, and related issues and based on my (limited) understanding of the issue, I think that compiling with NumPy 2.0 will generate binaries that work with both NumPy >= 2.0 and NumPy < 2.0. As a downstream user of h5py I've been using this repo to use h5py nightlies (which I assume is managed by h5py maintainers?):
It has been possible for some months (and thus seemingly reliable by now) to get a 2.0.0.dev NumPy from https://pypi.anaconda.org/scientific-python-nightly-wheels/simple, and many other libraries (scikit-learn, scipy, etc.) now build their nightly wheels against itn. Would it be possible to migrate the rackcdn.com h5py binaries to build against NumPy 2.0.0.dev? Then downstream libraries (like mine) could resume testing against NumPy 2.0.0.dev plus h5py (and anything that depends on it). Currently we have to choose between testing NumPy 2.0.0.dev or h5py because libraries that build against NumPy < 2.0 (like h5py on rackcdn) can't be imported when using the NumPy 2.0.0.dev wheels.