On Tue, Oct 1, 2013 at 4:43 AM, Nathaniel Smith <njs@pobox.com> wrote:

On Mon, Sep 30, 2013 at 10:51 PM, Christoph Gohlke <cgohlke@uci.edu> wrote:
> 2) Bottleneck 0.7.0
>
> https://github.com/kwgoodman/bottleneck/issues/71#issuecomment-25331701

I can't tell if these are real bugs in numpy, or tests checking that
bottleneck is bug-for-bug compatible with old numpy and we just fixed
some bugs, or what. It's clearly something to do with the
nanarg{max,min} rewrite -- @charris, do you know what's going on here?

Yes ;) The previous behaviour of nanarg for all-nan axis was to cast nan to intp when the result was an array, and return nan when a scalar. The current behaviour is to return the most negative value of intp as an error marker in both cases and raise a warning. It is a change in behavior, but I think one that needs to be made.

Chuck