Martin Schuck
Martin Schuck
Sorry for taking so long, had a lot going on recently. I have now split up the testing into a separate PR #22939. The PR is optimized to reduce the...
Is there anything still blocking 3.13 adoption? Tensorstore now has a wheel for 3.13 (see [here](https://github.com/google/tensorstore/commit/69d7d0573b4b093e60f41d1d57cf3a3a9039d6ea)) and Python 3.8 (and 3.9) support was dropped in #1333 for other reasons.
Is mujoco-py blocking the transition because of incompatibility issues?
Reviving this issue as we are currently facing the limitation in https://github.com/scipy/scipy/pull/23425. Is there any movement on this? The case for `__setitem__` semantics with integer arrays seems both sensible and...
Ah right, then maybe this is a topic for array-api-extra instead. Because this pattern should be common in most frameworks: ```python import array_api_strict as xp import jax.numpy as jp x...
Using the current spec, is there an array API-compatible way to implement this feature though? Because swapping the last line with ```python import array_api_extra as xpx ... new_x = xpx.at(x)[idx,...
That would be great. Should I open an issue in array-api-extra?
Alright, will do if I find the time.
I played around with the issue for a bit and encountered the following situation: ```python import jax.numpy as jnp import numpy as np x = jnp.asarray([0.0, 1.0]) y = jnp.asarray([2.0,...
Thanks for the thorough explanation and the references. The thought was to add a workaround in array-api-extra, but given the situation that's obviously not possible. One follow-up question: Is the...