Note that this is the first formal proposal to accept a NEP using our new process (yay!). While writing it I realized that the current text about this in NEP 0 is a bit terse, so I've also just submitted a PR to expand that section: https://github.com/numpy/numpy/pull/11459 -n On Fri, Jun 29, 2018 at 3:18 PM, Nathaniel Smith <njs@pobox.com> wrote:
Hi all,
I propose that we accept NEP 15: Merging multiarray and umath:
http://www.numpy.org/neps/nep-0015-merge-multiarray-umath.html
The core part of this proposal was uncontroversial. The main point of discussion was whether it was OK to deprecate set_numeric_ops, or whether it had some legitimate use cases. The conclusion was that in all the cases where set_numeric_ops is useful, PyUFunc_ReplaceLoopBySignature is a strictly better alternative, so there's no reason not to deprecate set_numeric_ops. So at this point I think the whole proposal is uncontroversial, and we can go ahead and accept it.
If there are no substantive objections within 7 days from this email, then the NEP will be accepted; see NEP 0 for more details: http://www.numpy.org/neps/nep-0000.html
-n
-- Nathaniel J. Smith -- https://vorpus.org
-- Nathaniel J. Smith -- https://vorpus.org