Unpin numpy<2

[joshmoore]

Using an issue on this repo as a high-level

• Enforce numpy is lower than 2.0.0 omero-py#414
• Remove numpy from tests_require in setup.py omero-figure#568
• Pin numpy<2 in setup.py ome-zarr-py#385
• cap numpy to less than 2 napari-ome-zarr#110
• omero-py v5.19.3 conda-forge/omero-py-feedstock#22

cc: @jburel @will-moore @sbesson

[sbesson]

For reference the migration guide has been published. Learning from the NumPy 2.0.0 story, I suspect the next iteration should probably be numpy<2 -> numpy<3 rather than completely unpinning the dependency

[joshmoore]

👍 on the pinning to the next major. Might also be worth keeping an eye on scientific-python/specs#217

[sbesson]

For reference, as we were starting to look into Python 3.13, came across https://numpy.org/devdocs/release/2.1.0-notes.html#numpy-2-1-0-release-notes

NumPy 2.1.0 provides support for the upcoming Python 3.13 release and drops support for Python 3.9.

So supporting Python 3.13+ will probably force us to start looking at bumping this dependency and the implications across the OMERO Python stack.
/cc @chris-allan

[chris-allan]

👍

There are several projects that have started to unpin or set >2 so the issue will only start to get worse not better. Most recent one for me was TileDB.