Matthew Barber
Matthew Barber
Ok, the idea of this PR is to maybe resolve #411. A few things have come up that might make folk think ultimately a first-party package is a bad idea....
Might of missed this in another issue/PR, but [GitHub releases](https://github.com/HypothesisWorks/hypothesis/releases) don't seem to of been updated since `6.74.0` around April.
Currently the suite fails when signatures use different arg names then whats in the spec for pos-only args, even though it shouldn't really matter. For example, testing a function with...
Per https://github.com/data-apis/array-api/pull/766#issuecomment-2018281825, not to merge yet as that PR isn't merge yet, and this is more of a POC to rework into the primary indexing tests possibly.
- Firstly we really need to - [x] Replace `numpy.array_api` with [`array-api-strict`](https://github.com/data-apis/array-api-strict) - `numpy.array_api` is going to be removed and supplanted by this third-party library - As bought up in...
As identified in https://github.com/data-apis/array-api-tests/pull/101#issuecomment-1949511287 we'll need to update `test_sum`, `test_prod` and `test_trace` because of https://github.com/data-apis/array-api/issues/731
The test suite has excellent coverage of the first `2021.12` spec release, but hasn't been updated to cover all the `2022.12` additions and changes. The following is a list of...
The test suite is mostly made up of test methods for each function (or array object method) in the spec. The majority of these tests require other functions to do...
In #104 we introduce a git submodule of the [`array-api`](https://github.com/data-apis/array-api/) repo, which going forward is required for the test suite to function (e.g. special case tests). This is not ideal...
Low prio until we get an actually implementation that supports the copy kwarg properly in `asarray()`, let alone `reshape()`. A util should be created to refactor what was already done...