1 Pull request merged by 1 person

• docs: fix indexing kwarg typing in meshgrid

  #915 merged Apr 3, 2025

6 Pull requests opened by 4 people

• docs: clarify that behavior when provided a nested sequence to `asarray` is unspecified

  #917 opened Mar 28, 2025

• docs: clarify input arrays in device placement

  #919 opened Apr 1, 2025

• `__setitem__` type promotion rules for array values

  #920 opened Apr 3, 2025

• TYP: fix type signature of eigh

  #924 opened Apr 9, 2025

• docs: `clip()` with scalar min/max clarifications

  #926 opened Apr 14, 2025

• fix: remove recommendation of no other public names in namespace

  #931 opened Apr 19, 2025

1 Issue closed by 2 people

• RFC: array-agnostic `quantile`

  #795 closed Mar 30, 2025

11 Issues opened by 7 people

• Should broadcast_arrays return a tuple instead of a list?

  #934 opened Apr 26, 2025

• `diff` to allow Python scalar or 0d array `append` and `prepend`?

  #930 opened Apr 18, 2025

• Boolean indexing when elements of mask shape are zero?

  #929 opened Apr 18, 2025

• Remove recommendation of no other public names in namespace

  #928 opened Apr 17, 2025

• Standardize "pinned" dtype promotions

  #927 opened Apr 15, 2025

• `clip`: ambiguous wording for scalar min/max

  #925 opened Apr 11, 2025

• clarify if `__array_namespace_info().default_device()` can be None

  #923 opened Apr 9, 2025

• Wrong return type for `linalg.eigh` in function signature

  #922 opened Apr 7, 2025

• Spell out where views are allowed

  #921 opened Apr 4, 2025

• Allow Python integer return for `count_nonzero(arr, axis=None)`

  #932 opened Apr 2, 2025

• Multi-device support meta-thread

  #918 opened Mar 31, 2025

13 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Add specification for the `__binsparse__` protocol

  #912 commented on Apr 3, 2025 • 15 new comments

• Clarify definitions of "default device" and "current device"

  #835 commented on Apr 1, 2025 • 0 new comments

• RFC: add array support for the `shift` kwarg in `roll`

  #914 commented on Apr 2, 2025 • 0 new comments

• finfo should not require float type for the result fields

  #405 commented on Apr 2, 2025 • 0 new comments

• RFC: define behavior for `__setitem__` when the assigned value promotes to the array's dtype

  #916 commented on Apr 3, 2025 • 0 new comments

• RFC: assignment via integer array indexing

  #864 commented on Apr 3, 2025 • 0 new comments

• RFC: specify expected behavior for `matrix_norm` and `vector_norm` when provided an empty array

  #901 commented on Apr 3, 2025 • 0 new comments

• RFC: special function extension

  #725 commented on Apr 3, 2025 • 0 new comments

• RFC: update `vecdot` to accept `keepdims` and `axis` to support tuples

  #910 commented on Apr 3, 2025 • 0 new comments

• Community meetings

  #853 commented on Apr 3, 2025 • 0 new comments

• RFC: In-memory sparse array interchange

  #840 commented on Apr 4, 2025 • 0 new comments

• RFC: add `"mutable arrays"` to `capabilities`

  #845 commented on Apr 4, 2025 • 0 new comments

• RFC: update `full` to accept 0D arrays for `fill_value`

  #909 commented on Apr 19, 2025 • 0 new comments