-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NumPy 2.0 compatibility #1964
Comments
You can install numpy 2.0.0rc1 from PyPI now, with |
@rgommers Thanks for pointing us to this! Just tested. Got error:
This is probably an issue in h5py, a dependency of scikit-bio. I saw this discussion in the h5py codebase. We probably need to wait until after they release a NumPy 2.0 compatible version. @wasade |
Thanks for testing @qiyunzhu. Good to know about |
@rgommers Update: I was able to install numpy 2.0.0rc1 and compatible versions of scipy, pandas and h5py. Then got the following error when importing scikit-bio:
We have planned to replace the |
Not too much more than what the error message says:
in the Cython file where this error comes from, I assume there's a |
|
Thanks for the update! Now we are waiting for Pandas 2.2.2. Then we add numpy 2.0 support for the upstream package biom-format. Then we can unblock numpy 2.0 in scikit-bio. |
That's up on PyPI too now, since ~25 minutes ago. |
Hi @qiyunzhu, I just wanted to check in on this, and ask if you plan to include support in 0.6.1 or 0.7.0 (and, if you know, roughly when)? |
Thanks! I'm not 100% sure that the final numpy 2.0 release will take more than a month from now, so a release before the end of May would be safer. But if you've got all the problems resolved then that's already good to know. |
It seems that scikit-bio is compatible with the upcoming NumPy 2.0. Following this guideline, I ran:
And nothing happened, meaning the check passed. However, I haven't been able to actually install NumPy 2.0 for test (probably because it is still under active development). Therefore we should keep an eye on it.
Thanks @wasade for pointing out this.
The text was updated successfully, but these errors were encountered: