You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought it would be sufficient to test against strict and numpy, but there may be value in testing against PyTorch and maybe even CuPy. Perhaps the data issue we just fixed is unique, but it's hard to tell without trying. At the very least, it will expose shortcomings in either array_api_compat, array_api_strict, or the Array API Standard documentation). For instance, I immediately ran into data-apis/array-api-compat#226 today, and also found:
# These all work with strict# import array_api_strict as xpfromarray_api_compatimporttorchasxpx=xp.asarray(1, dtype=xp.uint32)
-x# RuntimeError: "neg_cpu" not implemented for 'UInt32'abs(x) # RuntimeError: "abs_cpu" not implemented for 'UInt32'~x# RuntimeError: "bitwise_not_cpu" not implemented for 'UInt32'
@lucascolley any chance you'd be interested in taking this on? I ask because you've worked on getting SciPy tests running on other arrays.
The text was updated successfully, but these errors were encountered:
I thought it would be sufficient to test against
strict
andnumpy
, but there may be value in testing against PyTorch and maybe even CuPy. Perhaps thedata
issue we just fixed is unique, but it's hard to tell without trying. At the very least, it will expose shortcomings in eitherarray_api_compat
,array_api_strict
, or the Array API Standard documentation). For instance, I immediately ran into data-apis/array-api-compat#226 today, and also found:@lucascolley any chance you'd be interested in taking this on? I ask because you've worked on getting SciPy tests running on other arrays.
The text was updated successfully, but these errors were encountered: