Skip to content

Enh: Update support for Array API to v2024. #858

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

Open
hameerabbasi opened this issue Apr 4, 2025 · 4 comments · May be fixed by #863
Open

Enh: Update support for Array API to v2024. #858

hameerabbasi opened this issue Apr 4, 2025 · 4 comments · May be fixed by #863
Labels
enhancement Indicates new feature requests

Comments

@hameerabbasi
Copy link
Collaborator

Please describe the purpose of the new feature or describe the problem to solve.

Right now, sparse has quite a good coverage of Array API v2022, but the latest revision is v2024.

Suggest a solution if possible.

Update support for Array API to v2024.

If you have tried alternatives, please describe them below.

No response

Additional information that may help us understand your needs.

No response

@hameerabbasi hameerabbasi added the enhancement Indicates new feature requests label Apr 4, 2025
@prady0t
Copy link
Contributor

prady0t commented Apr 9, 2025

There are now around 162 failed tests for the Numba backend as apposed to 65 earlier.

@hameerabbasi
Copy link
Collaborator Author

@prady0t You'd need to follow these steps to update the Array API support:

  • Update the commit hash of array-api-tests everywhere.
  • Run the tests, noting the common error messages.
  • There might be a few that are low-hanging fruit, which may be easily knocked out. Fix those first.
  • For others, add them to the appropriate xfails files.

@prady0t
Copy link
Contributor

prady0t commented Apr 9, 2025

For the first step, can we use export ARRAY_API_TESTS_VERSION="2024.12" (see) inside the test-array-api.sh script? It works for me locally.

@hameerabbasi
Copy link
Collaborator Author

I'd suggest updating the __array_api_version__ value in the appropriate Python file.

@prady0t prady0t linked a pull request Apr 10, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Indicates new feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants