Thanks for bringing this issue up!

I don't know if there's anything to be done here. The migration guide recommends using the ruff plugin: ruff check path/to/code/ --select NPY201. Upon using this command, I get "All checks passed!"

It looks like the current release version (the one that I checked) never made it to PyPI, because the deployment failed. I'll work on this today. Once it's up, I think we can add ourselves to the ecosystem support list.

One important thing to do is to fix the build-time metadata: https://github.com/scikit-sparse/scikit-sparse/blob/master/pyproject.toml#L33. You should depend on numpy>=2.0.0 for Python 3.9 and up, as documented at https://numpy.org/devdocs/dev/depending_on_numpy.html#numpy-2-0-specific-advice. That way you'll get wheels that are 1.x and 2.x compatible.

Thanks, @rgommers. I'll work on it.

Probably will want a release as well that includes those rebuilt wheels (with the metadata changes Ralf suggested)

The support has been present in the master branch for 9 months now, and seems fine. Sorry to ping again, but any chance we can have a new release? It looks like releases are sdist-only, so should be quick and easy?

Thanks for mentioning this @rgommers! I had a family event right around the time that I was working on this and forgot to make a new release. I've set the release now, and I'll make sure that it goes to PyPI.

I see the 0.4.16 release is up, thanks @AaronDJohnson! This issue can be closed now I think?