-
Notifications
You must be signed in to change notification settings - Fork 10
TST: NumPy 1.x support #169
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
Conversation
# Don't rely on OverflowError, as it is not guaranteed by the Array API. | ||
nrtol = int(1.0 / rtol) | ||
if nrtol > xp.iinfo(b.dtype).max: | ||
# rtol * max_int < 1, so it's inconsequential |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In practice, this impacts only array-api-strict wrapping around numpy 1.x
Yeah, I think we are still at a stage where we can require that only the latest versions work. But we'll get to this point eventually. |
I linked the issue suggesting that we test with oldest SPEC 0 NumPy. Pros/cons of that vs. the approach of |
That makes sense. Now testing vs. 1.25.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @crusaderky !
we should probably change the |
* TST: NumPy 1.x support * Downgrade to oldest SPEC0
Out of scope: we need to start a conversation about how array-api-compat, array-api-extra, and scipy are going to support obsolete versions of backends other than NumPy.