Support 2023.12 version of the array API

[honno]

The array API has just had its 2023.12 release (data-apis/array-api#755)... in Feb 2024 😅 This PR simply accepts api_version="2023.12" for extra.array_api.make_strategies_namespace().

---

I believe there aren't any changes that should necessitate what the strategies namespace is doing for 2023.12! I assume this will be an on-going trend, as I can't think of any existing discussions that would either shake-up the existing strategies or want us to add news ones.

I did have the idea to maybe just warn instead of erroring when api_version is greater than the last item of RELEASED_VERSIONS (and not draft), so we don't "annoy" libraries by asking them to use an older api_version kwarg for make_strategies_namespace() whilst they wait on us to update one variable upstream for a very trivial change 🤔 I'm really not sure and might be something to just see how future array API iterations play out first.

---

It's also worth noting that numpy.array_api will most likely be removed at some point (numpy/numpy#25542) and superseded by the new array-api-strict third-party package. As that library is "official" and pretty stable (esp. for the purposes of what extra.array_api does), is that something we'd want for CI @Zac-HD? If so, I can try work out how to do CI things with some direction.

There's also array-api-compat which could be a good start in covering libraries other than NumPy (CuPy, PyTorch, Dask, possibly more in the future). I'll be having a think on it generally for the array API test suite (data-apis/array-api-tests#235) anywho.

[Zac-HD]

a few docs suggestions:

[Zac-HD]

It's also worth noting that numpy.array_api will most likely be removed at some point (numpy/numpy#25542) and superseded by the new array-api-strict third-party package. As that library is "official" and pretty stable (esp. for the purposes of what extra.array_api does), is that something we'd want for CI @Zac-HD? If so, I can try work out how to do CI things with some direction.

Yeah, I'm happy to depend on that for our tests; open a PR whenever suits you 🙂

There's also array-api-compat which could be a good start in covering libraries other than NumPy (CuPy, PyTorch, Dask, possibly more in the future). I'll be having a think on it generally for the array API test suite (data-apis/array-api-tests#235) anywho.

Ooooh, also nice. Definitely interested, but I trust your judgement and will leave details and implementation order to you.

[Zac-HD]

Thanks again @honno! I always feel that Hypothesis - and the wider ecosystem - is so lucky to have you maintaining this stuff ♥️