<html xmlns="http://www.w3.org/1999/xhtml"><head> <title></title> <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no"> </head> <body><div id="CanaryBody"> <div> Hey Stephan,</div><div><br></div><div>After some discussion with Ralf, I feel that the best way forward would be to add the __numpy_implementation__ (which is my preferred name for it). While I consider the interface final (or at least to the point where we would only add functionality and not remove it), I would prefer to keep the experimental tag, for this very reason: Avoiding having to write a new NEP for adding functionality.</div><div><br></div><div>However, I’m open to declaring it non-experimental it as well.</div> <div><br></div> </div> <div id="CanarySig" style="left: 0px; touch-action: auto; -webkit-touch-callout: none; -webkit-user-drag: none; -webkit-tap-highlight-color: rgba(0, 0, 0, 0);"> <div> <div style="font-family:Helvetica;color:#000;font-size:13px;">Best Regards,<div>Hameer Abbasi</div></div> <div><br></div> </div> </div> <div id="CanaryDropbox"> </div> <blockquote id="CanaryBlockquote"> <div> <div>On Sunday, Apr 28, 2019 at 5:50 AM, Stephan Hoyer <<a href="mailto:shoyer@gmail.com">shoyer@gmail.com</a>> wrote:<br></div> <div><div dir="ltr"><div dir="ltr">On Sat, Apr 27, 2019 at 4:39 PM Hameer Abbasi <<a href="mailto:einstein.edison@gmail.com">einstein.edison@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div style="font-family:Helvetica;color:rgb(0,0,0);font-size:13px"><blockquote id="gmail-m_-7798603087801193569"><div><div>On Saturday, Apr 27, 2019 at 6:21 PM, Stephan Hoyer <<a href="mailto:shoyer@gmail.com" target="_blank">shoyer@gmail.com</a>> wrote:</div><div><div dir="ltr"><div class="gmail_quote"><div>Are there aspects of your uarray proposal that are relevant to the current proposed revisions to NEP 18? If so, please restate them :).</div></div></div></div></div></blockquote><div><br></div><div><div>Of course, here’s my proposal:</div><div><br></div><div>We leave NEP-18 as-is for now, and instead of writing separate protocols for coercion, dtypes and ufuncs (which will be needed somewhere down the line), we have a discussion about uarray and see if it can help there. :-)</div></div></div></blockquote><div><br></div><div>I don't want to add separate protocols for coercion, dtypes or ufuncs as part of NEP-18. Whatever form these should take, they should definitely be a separate proposals.</div><div><br></div><div>__array_function__ is not the end of the story about duck array support in NumPy, but I think it's valuable incremental step, as evidenced by the projects that are already eager to adopt it. I would really, really like to try to get a usable and near-final version of it released in NumPy 1.17. That doesn't leave us much time.</div><div><br></div><div>I've very interested in your work on uarray, but as far as I can tell, it would not directly interact with NumPy's implementation of __array_function__, so discussing it doesn't feel immediately urgent to me. Rather, it's an alternative and possibly more complete solution for some of the same problems. That's fantastic -- but please, let us finish __array_function__ first.</div></div></div> _______________________________________________ <br>NumPy-Discussion mailing list <br>NumPy-Discussion@python.org <br>https://mail.python.org/mailman/listinfo/numpy-discussion <br></div> </div> </blockquote> </body></html>