Right, let me elaborate a bit more... sorry for being unclear.

Unfortunately we don't have anyone to just take over writing tests and and
things like that -- we're all just random people contributing a bit of time
to try and keep things working. And unfortunately there are more things to
do than there are people to do them, so only those things happen which
someone sits down and decides to champion. For example I try to spend what
time I can on reviewing changes and encouraging new contributors, but that
pretty much takes all the time I have for numpy stuff. None of the changes
in this PR really affect me directly outside of that, so I probably won't
pick them up myself if you decide to leave them. Maybe someone else will,
though, or maybe not; I don't know.

Really they are not far from being useful -- they just need a bit more
polishing before we can accept them, and then they'll become part of
mainline numpy and you won't have to worry about tracking them for your own
users anymore. So it'd be great if you're able to do that (and then as a
bonus you'll be familiar with the process for the next time you run into
some issues like this). But if not then we understand that too!

On Fri, Mar 22, 2013 at 1:20 PM, Åke Sandgren <notifications@github.com>wrote:

> In numpy/core/src/umath/funcs.inc.src:
>
> > @@ -360,8 +360,7 @@ nc_pow@c@(@ctype@ *a, @ctype@ *b, @ctype@ *r)
> >              *r = npy_cpack@c@(NPY_NAN, NPY_NAN);
> >
> >              /* Raise invalid */
> > -            ar = NPY_INFINITY;
> > -            ar = ar - ar;
> > +	    npy_set_floatstatus_invalid();
>
> Well, you can always copy the diff into a file and add it by hand if you
> want to...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/3163/files#r3489074>
> .
>