On Fri, May 23, 2008 at 11:44 AM, Robert Kern <[EMAIL PROTECTED]> wrote: > On Fri, May 23, 2008 at 12:22 PM, Keith Goodman <[EMAIL PROTECTED]> wrote: > >> But the first example >> >>>> x = mp.matrix([[mp.nan]]) >>>> x >> matrix([[ NaN]]) >>>> x.all() >> True >>>> x.any() >> True >> >> is still surprising. > > On non-boolean arrays, .all() and .any() check each element to see if > it is not equal to 0. NaN != 0. Returning False would be just as > wrong. If there were a Maybe in addition to True and False, then > perhaps that would be worth changing, but I don't see a reason to > change the rule as it is.
That makes sense. Hopefully it will find its way into the doc string. If I want NaNs to be False I can always do (x == x).all() instead of x.all() _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
