Athan
Hey everyone, We're back from our August recess and will be having a workgroup meeting this Thursday, 4 September. Please be sure to add any agenda topics that you'd like...
@ev-br #900 doesn't cover setitem semantics, however.
@ev-br The spec likely reflects pre-NumPy v2.0. See https://numpy.org/doc/1.26/reference/generated/numpy.meshgrid.html and https://github.com/numpy/numpy/blob/v1.26.0/numpy/lib/function_base.py#L5163.
Currently, in the specification, the list is as follows: - meshgrid - broadcast_arrays - info.devices In the following APIs, we return tuples: - unique_all - unique_counts - unique_inverse - nonzero...
I've opened https://github.com/data-apis/array-api/pull/981.
The current guidance originates from NumPy (see https://numpy.org/doc/1.26/reference/generated/numpy.concatenate.html). > The arrays must have the same shape, except in the dimension corresponding to axis (the first, by default).
@gunjjoshi Would you mind doing one more pass over this PR?
I think the option of using bold text should suffice. While all-caps is a common convention, it does add a fair amount of visual noise. I think encoding RFC terms...
@jacksonloper Thanks for the ping. Just need to find time to review. If this is needed for what you are working on, I can bump it up in the queue.
While `take_along_axis` may not be used on its own in SciPy, it is commonly used indirectly. For example, as @mdhaber mentioned offline, it is used in `rankdata` (see https://github.com/scipy/scipy/pull/20639), which...