-
Notifications
You must be signed in to change notification settings - Fork 2
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
(Array API support): Add __array_namespace_info__
and device
#101
Conversation
0f7e5a5
to
d6e841e
Compare
ndonnx/_info.py
Outdated
# We don't support complex numbers yet due to immaturity in the ONNX ecoystem, so "complex floating" is meaningless. | ||
# The Array API standard requires this key to be present so we set it to None. | ||
"complex floating": None, |
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.
Returning something wrong is still not compliant with the standard, but it might lead to issues that are harder to debug than what one would get if the key were just missing. I think we should rather not return "complex floating"
as a key.
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 do agree however the tests as they stand explicitly assert all the keys are present. See data-apis/array-api-tests#337.
642c7a4
to
5f91aed
Compare
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, Looks good! I just have a few more minor suggestions.
ndonnx/_info.py
Outdated
ndx.uint64, | ||
] | ||
|
||
def capabilities(self) -> dict: |
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.
def capabilities(self) -> dict: | |
def capabilities(self) -> dict[str, bool]: |
7b7f930
to
4f6570c
Compare
Co-authored-by: Christian Bourjau <[email protected]>
Co-authored-by: Christian Bourjau <[email protected]>
Continues with #6.