-
Notifications
You must be signed in to change notification settings - Fork 34
Minimum NumPy version support? #21
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
Comments
+1 for supporting older versions where possible. Probably back to all supported versions according to NEP 29 - so testing NumPy 1.21 would be useful. That may mean a few things don't work of course - a non-default value of the |
The mean reason I hadn't tested older NumPy's is because we can't use |
Well testing was a good idea because I found at least one other broken thing ( |
Which cupy versions should we support? |
So it turns out that
If any of these are an issue for you, I recommend bumping your minimum NumPy version, as I do not intend to work around them here (I suppose we could work around some of the simpler ones if it's really important). |
The items listed in #21 (comment) that do not work in NumPy 1.21 are not issues with scikit-learn's codebase. |
We now support and test numpy 1.21. |
Currently
unique_*
passesequal_nan
tonp.unique
, which was introduced in NumPy 1.24 (released 12/2022).array-api-compat/array_api_compat/common/_aliases.py
Lines 184 to 190 in 945609e
Does
array-api-compat
want to support older versions of NumPy?The text was updated successfully, but these errors were encountered: