Only support NumPy 2.0 as a backend

Open
#21 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
numpy, python
Domain
backend

Research direction

First confirm that NumPy 2.0 is released, stable, and broadly supported by the surrounding ecosystem. Then locate the NumPy backend compatibility code in array-api-strict and remove the NumPy 1.26 paths while preserving the strictness-related behavior; done means the project supports only NumPy 2.0 as its backend and its checks pass.

Written by the indexing model from the issue text.

Description

Medium Priority

Obviously not just yet, but once NumPy 2.0 is released and stable, we should drop support for NumPy 1.26 as a backend. That would allow us to remove all the compatibility code and only have code related to strictness.

The actual backend in array-api-strict doesn't really matter that much, but this would limit the usability for libraries that use NumPy internally in addition to the array API, so we should only do this once the ecosystem seems generally caught up on NumPy 2.0 support.

Dominant language
Python
Stars
34
Forks
14
Avg merge
3m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from data-apis/array-api-strict

All issues in data-apis/array-api-strict

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.