[Numpy-discussion] Experimental =?utf-8?Q?=60like=3D=60_?=attribute for array creation functions
einstein.edison at gmail.com
Mon Aug 10 11:35:14 EDT 2020
We should have a higher-bandwidth meeting/communication for all stakeholders, and particularly some library authors, to see what would be good for them.
We should definitely have language in the NEP that says it won’t be in a release unless the NEP is accepted.
Sent from Canary (https://canarymail.io)
> On Monday, Aug 10, 2020 at 5:31 PM, Sebastian Berg <sebastian at sipsolutions.net (mailto:sebastian at sipsolutions.net)> wrote:
> Hi all,
> as a heads up that Peter Entschev has a PR open to add `like=` to
> most array creation functions, my current plan is to merge it soon as a preliminary API and bring it up again before the actual release (in a few months). This allows overriding for array-likes, e.g. it will allow:
> arr = np.asarray(, like=dask_array)
> type(arr) is dask.array.Array
> This was proposed in NEP 35:
> Although that has not been accepted as of now, the PR is:
> This was discussed in a smaller group, and is an attempt to see how we
> can make the array-function protocol viable to allow packages such as
> sklearn to work with non-NumPy arrays.
> As of now, this would be experimental and can revisit it before the
> actual NumPy release. We should probably discuss accepting NEP 35
> more. At this time, I hope that we can put in the functionality to
> facilitate this discussion, rather the other way around.
> If anyone feels nervous about this step, I would be happy to document
> that we will not include it in the next release unless the NEP is
> accepted first, or at least hide it behind an environment variable.
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion