diff options
author | Peter Andreas Entschev <peter@entschev.com> | 2019-08-05 16:27:31 +0200 |
---|---|---|
committer | Sebastian Berg <sebastian@sipsolutions.net> | 2019-08-05 09:27:31 -0500 |
commit | 044f5131450f38cdfbab63d6999b60e7e3bbabe5 (patch) | |
tree | b5c21acef0796eda716860b890897f29e90f545a /numpy/lib/arraypad.py | |
parent | 57feadb1f8f25b4e34d2085646cf2a78ad3654a8 (diff) | |
download | numpy-044f5131450f38cdfbab63d6999b60e7e3bbabe5.tar.gz |
NEP: Proposal for __duckarray__ protocol (#14170)
This NEP proposes the introduction of the __duckarray__ protocol, as described in high-level by NEP-22 and further discussed in #13831 .
We have another idea by @shoyer on how to handle duck array typing through __array_function__, as mentioned in #13831 (comment):
we could consider adding a like argument to duckarray. That would require changing the protocol from the simplified proposal above -- maybe to use array_function instead of a dedicated protocol like duckarray? I haven't really thought this through.
The idea above seems viable, and perhaps more complete as well. That said, I want to either extend this NEP to cover that, or maybe write a separate NEP so we can discuss and judge which one is a better solution. In the meantime, let's start discussing the text here.
Diffstat (limited to 'numpy/lib/arraypad.py')
0 files changed, 0 insertions, 0 deletions