-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix array API inspection behavior with device
keyword
#1979
Fix array API inspection behavior with device
keyword
#1979
Conversation
* Fixes a bug where `"complex128"` was present in the list of dtypes on devices without fp64 support * Fixes functionality of device keyword for SyclQueue and strings * Improves error message when device keyword cannot be used to construct a SyclDevice instance * Tweaks docstring for device keywords in inspection utilities
Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞 |
Array API standard conformance tests for dpctl=0.19.0dev0=py310h93fe807_493 ran successfully. |
Array API standard conformance tests for dpctl=0.19.0dev0=py310h93fe807_494 ran successfully. |
@antonwolfy |
Array API standard conformance tests for dpctl=0.19.0dev0=py310h93fe807_496 ran successfully. |
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.
I checked with dpnp changes added in dpnp-2275 and it works as expected now.
Thank you @ndgrigorian for a quick fix. LGTM!
This PR proposes changing the handling of the
device
keyword in the array API inspection utilities to:Also fixes the
dtypes
utility returningcomplex128
in its output when the provided device does not support double precision types.Resolves #1978 , resolves #1977