Hi all,
Our bi-weekly triage-focused NumPy development meeting is Wednesday,
June 16nd at 11 am Pacific Time (18:00 UTC).
Everyone is invited to join in and edit the work-in-progress meeting
topics and notes:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg
I encourage everyone to notify us of issues or
Hi all,
(sorry for the length, details/discussion below)
On the triage call, there seemed a preference to just try to skip the
deprecation and introduce `copy="never"`, `copy="if_needed"`, and
`copy="always"` (i.e. string options for the `copy` keyword argument).
Strictly speaking, this is again
Hi all!
Our Newcomer's Meeting tomorrow,
* June 17, will take place at 4pm UTC (instead of the usual 8pm UTC).*
This new time is meant to be more inclusive to contributors in different
time zones. I think it would be nice to experiment with alternating times
for this meeting, so I'll update the c
On Wed, Jun 16, 2021 at 1:01 PM Sebastian Berg
wrote:
> 2. We introduce `copy="never"`, `copy="if_needed"` and `copy="always"`
>as strings (all other strings will be a `TypeError`):
>
>* Problem: `copy="never"` currently means `copy=True` (the opposite)
>Which means new co
I agree with Stephan, but even 3 seems dangerous to me. Any code that wraps
a numpy function and accepts a `copy` parameter (especially
`__array_function__`) is likely to contain `if copy` somewhere, which would
result in entirely (but likely silently) the wrong behavior for
`copy="never"`. An impo
