Ralf Gommers wrote:
> This sounds quite reasonable to me. The `k=0` keyword is quite badly named,
> which is my one concern. Especially when tacking it on at the end of a
> signature with already 3-4 keywords, it's not a good name. How about
> something like `diag_offset`?
FWIW, we chose `offset`
> The new discrepancy between `arr.T` and `arr.transpose()` is justified, as
> `T` is defined by the Array API, where `transpose` isn't and should retain
> the existing behavior.
The other side of the coin here is that this change would fix the
discrepancy between `arr.T` and the functions `np.ma
If NumPy were to make a move on the deprecation, then I think it would be
reasonable to change the standard from
> If the array instance is not two-dimensional, an error should be raised.
to “if the array instance is not two-dimensional, behaviour should match `.mT`,
or an error should be raise
