Thanks @lithomas1

@lithomas1 @mroeschke this doesn't look correct to me. I just checked one CI log and it shows this after the "before build" step (re-installs numpy 1.26.4):

     Successfully installed Cython-3.0.9 meson-1.2.1 meson-python-0.13.1 numpy-1.26.4 packaging-24.0 pyproject-metadata-0.7.1 tomli-2.0.1 versioneer-0.29 wheel-0.43.0
    Installing build dependencies: finished with status 'done'

This is due to build isolation. The [build-requires] section in pyproject.toml needs updating instead, it needs something like "numpy>=2.0.0rc1,<2.3", (or <3 if you prefer) EDIT: in release branches, and "numpy>=2.0.0rc1 in main. I recommend copying what SciPy does (except change 2.0.0b1 to 2.0.0rc1 now):
https://github.com/scipy/scipy/blob/2a8c4ca6edceba5daaac60bbd213a84e7c03c361/pyproject.toml#L28-L34

@lithomas1 @mroeschke this doesn't look correct to me. I just checked one CI log and it shows this after the "before build" step (re-installs numpy 1.26.4):

     Successfully installed Cython-3.0.9 meson-1.2.1 meson-python-0.13.1 numpy-1.26.4 packaging-24.0 pyproject-metadata-0.7.1 tomli-2.0.1 versioneer-0.29 wheel-0.43.0
    Installing build dependencies: finished with status 'done'

This is due to build isolation. The [build-requires] section in pyproject.toml needs updating instead, it needs something like "numpy>=2.0.0rc1,<2.3", (or <3 if you prefer) EDIT: in release branches, and "numpy>=2.0.0rc1 in main. I recommend copying what SciPy does (except change 2.0.0b1 to 2.0.0rc1 now): https://github.com/scipy/scipy/blob/2a8c4ca6edceba5daaac60bbd213a84e7c03c361/pyproject.toml#L28-L34

Nice catch, thanks!

I was thinking in my head that editable installations would be messed up by the build-requires, but that obviously uses -no-build-isolation 🤦 .

I'll put up another PR fixing this.