[Numpy-discussion] Fast clip for native types, 2d version

Robert Kern robert.kern at gmail.com
Sun Jan 14 22:07:55 CST 2007


David Cournapeau wrote:
> Robert Kern wrote:
>> David Cournapeau wrote:
>>
>>>   2: the old implementation does not upcast the input array. If the
>>> input is int32, and min/max are float32, the function fails; if input is
>>> float32, and min/max float64, the output is still float32. Again, this
>>> seems against the expected numpy behaviour ?
>> The latter is expected. As discussed previously here, 
> Could you tell me where this was discussed, I think I missed it.

http://projects.scipy.org/pipermail/numpy-discussion/2006-November/024402.html

> Thanks for the precision. Is this the expected behaviour for endianness, 
> too ?

What endianness behaviour?

> And why integer input works for float64 but not for float32 ?

As I said, I don't know.

-- 
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