-
Notifications
You must be signed in to change notification settings - Fork 34
2022.12 support #38
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
2022.12 support #38
Conversation
@asmeurer are you also adding |
The test suite doesn't check anything yet, but assuming |
Thanks to work from @honno at data-apis/array-api-tests#184, I have some updates on pytorch complex numbers support: The following torch functions do not support complex numbers:
|
That's probably caused by torch.unique sorting by default and having a keyword for it; sorting won't work with complex dtypes. Not too relevant for the standard, but a pain to get to work indeed in a wrapper. So I agree with your decisions here. |
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.
LGTM!
Regarding array_api_compat.torch.take()
, IIRC index_put()
wasn't quite adequate for "full" NumPy compat and I ended up using torch.Tensor.__get__()
(Quansight-Labs/numpy_pytorch_interop#96), but it's not that surprising if it's fine for the Array API scope. I'm sure attempted-adoption in SciPy will be a brilliant way to battle-test array_api_compat.torch.take()
in the end anywho, just note my test_take
does have a few limitations...
We figured out @tupui's isdtype issue. It was related to a version of the function that he had implemented in scipy. It seems there aren't any issues with the version in the compat library. So we can go ahead and do a release here. |
This is still WIP because we need some fixes to the test suite.