[Numpy-discussion] NEP 30 - Duck Typing for NumPy Arrays - Implementation

Hi, we have a new proposal for the implementation of NumPy array duck typing [1] [2], following the high-level overview described in NEP-22 [3]. Would be great to get some comments on that. [1] https://github.com/numpy/numpy/blob/master/doc/neps/nep-0030-duck-array-protocol.rst [2] https://gith

Re: [Numpy-discussion] NEP 30 - Duck Typing for NumPy Arrays - Implementation

Hi Peter, thanks for writing that up! On Mon, Aug 5, 2019 at 8:07 AM Peter Andreas Entschev wrote: > Hi, > > we have a new proposal for the implementation of NumPy array duck > typing [1] [2], following the high-level overview described in NEP-22 > [3]. > A couple of high level comments: Havi

[Numpy-discussion] proposal to accept NEP 28 (numpy.org website redesign)

Hi all, I propose to accept NEP 28 (https://github.com/numpy/numpy/pull/14032). Discussion seems to have died down, and there have been no major objections raised. In addition to the discussion on the PR, we had some discussion on translations in the community call 1.5 weeks ago. We decided that

Re: [Numpy-discussion] NEP 30 - Duck Typing for NumPy Arrays - Implementation

On Mon, Aug 5, 2019 at 2:48 PM Ralf Gommers wrote: > Having __array__ give a TypeError is fine for libraries that want to > prevent unintentional coercion with, e.g., `np.asarray(my_ducktype)`. > However that leaves the obvious question of what the right way is to do > this intentionally. Would b

[Numpy-discussion] did anyone create numpy.slack.com?

Hi all, I was trying to create a Slack workspace named numpy, but it turns out that numpy.slack.com already exists. Does anyone have access to it or knows who is administering it? Thanks, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.or