What state is master in if this doesn't get merged? Would leaving this out
of 1.9 mean that we release 1.9 with a broken __numpy_ufunc__ API and get
stuck in some compatibility trap?


On Fri, May 9, 2014 at 8:34 PM, Blake Griffith <notifications@github.com>wrote:

> In numpy/core/tests/test_umath.py:
>
> > -        assert_equal(res, "reduce")
> > -
> > -        res = np.multiply.accumulate(a, 1)
> > -        assert_equal(res, "accumulate")
> > -
> > -        res = np.multiply.reduceat(a, 1)
> > -        assert_equal(res, "reduceat")
> > +        res = np.multiply.__call__(1, a)
> > +        assert_equal(res[0], a)
> > +        assert_equal(res[1], np.multiply)
> > +        assert_equal(res[2], '__call__')
> > +        assert_equal(res[3], 1)
> > +        assert_equal(res[4], (1, a))
> > +        assert_equal(res[5], {})
> > +
> > +        res = np.multiply.reduce(a, 'axis0', 'dtype0', 'out0', 'keep0')
>
> Working on it. I implemented at with the last arg as a kwarg which is
> incorrect.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/4626/files#r12492498>
> .
>



-- 
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org