[Numpy-discussion] numpy.nansum() behavior in 1.3.0
Robert Kern
robert.kern at gmail.com
Mon Jun 1 19:30:22 EDT 2009
On Mon, Jun 1, 2009 at 15:31, <josef.pktd at gmail.com> wrote:
> On Mon, Jun 1, 2009 at 4:06 PM, Alan G Isaac <aisaac at american.edu> wrote:
>> On 6/1/2009 3:38 PM josef.pktd at gmail.com apparently wrote:
>>> Here's a good one:
>>>
>>>>>> np.isnan([]).all()
>>> True
>>>>>> np.isnan([]).any()
>>> False
>>
>>
>> >>> all([])
>> True
>> >>> any([])
>> False
>
> also:
>
>>>> y
> array([], dtype=float64)
>>>> (y>0).all()
> True
>>>> (y>0).any()
> False
>>>> ((y>0)>0).sum()
> 0
>
> I don't know what's the logic, but it causes the bug in np.nansum.
You will have to special-case empty arrays, then.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the NumPy-Discussion
mailing list