On Mon, Aug 7, 2023 at 1:40 AM Andrew Nelson <andyf...@gmail.com> wrote:
> The array-api documentation ( > https://data-apis.org/array-api/latest/API_specification/generated/array_api.asarray.html#array_api.asarray) > for `asarray` has a copy keyword, the numpy version doesn't. Is there a > plan to add such a keyword to no.asarray? > > I guess this is part of a general question, how much numpy convergence > there will be to the array-api specifications over time? > Hi Andrew, the plan is for the main numpy namespace to be fully compatible with the array API standard in the 2.0 release. This was discussed in the 2.0 developer meeting in April; on this topic there is a slide deck available which covers the proposal and the needed changes: https://github.com/numpy/archive/tree/main/2.0_developer_meeting. The outcome of the discussion in that meeting is to go even a bit further and apply some of the key design principles (e.g., use of positional/keyword-only parameters and avoiding use of keyword to control the number or type of return values) also to numpy functions that aren't in the array API standard. A NEP is still to be written, but I'd expect it to not say much that's new compared to those slides and that discussion. There's still a fair bit of work to do, including the copy= keyword, and we have ~4 months or so left for that. Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
