Support Numpy2 API about slicer HOT 2 OPEN

Thanks for the information.

If you already have a pinned numpy version in Slicer builds, then you have no issues until next release, but users must be warned not to upgrade numpy in any way.

Slicer does indeed pin the numpy version as part of the build process. I’m sure if users post about problems on the discourse forum we can ask and recommend to not use numpy 2 if it is not compatible with Slicer yet.

Therefore, you shall block numpy upgrades in the pip_install function.

This could potentially be done if numpy is specified directly, however it would not cover all cases if say a user specifies to install some other package that happens to depend on numpy where that package may specify numpy >= 2. Slicer pip_install is not going to know about various python package dependencies.

from slicer.

If numpy maintainers do this right, making changes gradually (using deprecation warnings for several years before any breaking change takes effect) then the transition will be smooth. No packages will require numpy 2.x until all other packages already support numpy 2.x. In this case we will not need to do anything special in Slicer, just find a safe time to update Slicer's numpy to 2.x.

If numpy developers mess up the transition and there will be a time when many packages still only support numpy 1.x while some already require numpy 2.x then we'll see what we need to do, but I'm optimistic that numpy developers are smart enough to avoid this.

from slicer.