Loosen numpy dependency

[multimeric]

This fork enforces numpy < 2

python-javabridge/setup.py

Line 402 in dbe350b

'numpy<2',

Since numpy 2 was released 2 years ago and a few other packages have migrated, could we consider making this package compatible with numpy 2? It doesn't look like there is a tight coupling between this and numpy so I'm hoping this won't be too tricky.

Happy to take a look myself if maintainers approve.

[gnodar01]

Hi, sure feel free to create a PR. I'm unlikely to do this work myself anytime soon, since we have quasi-archived this project. I would however review submitted code, and merge it in after it passes QA.

I should however point out that there is in fact a tight coupling between this and numpy and likely a number of breaking changes. Additionally, although I am not totally sure, I do think that in order to be compatible with numpy > 2 you will also need to unpin cython and address any deprecations between version 0.29 and 3 (they went directly to v3, there are no versions 1 and 2). If you aren't already familiar with cython, or C-esque programming, then that will require learning at least a bit about how cython works, which isn't monumental, but also isn't super trivial.

Please only commit to doing a PR if you are willing to go through the linked migration guides thoroughly, and also learn the necessary bits of cython (if you aren't already familiar with it). Do not for instance try to use AI and submit un-inspected code just because tests pass.

You will need to bump the version of python-javabridge to 5.0.0 to avoid breaking downstream dependents.

[multimeric]

I take your point about this not being a priority for you. For better or worse I think this has become the de-facto version of this repo due to upstream being unmaintained and this having a pip package (not that Google results acknowledge that), making this the best place for a fix. I'll have a look at the code and see how big the changes might be.