[EMAIL PROTECTED] wrote:
>>> Raise a ValueError (even in 2.5, therefore risking to break something)
+1 as well
> it took me a while to figure out that some
> mysteriously appearing zeros were nans that were silently converted
> during casting to int.
and this is why -- a zero is a perfectly vali
On Dec 4, 2008, at 3:24 PM, [EMAIL PROTECTED] wrote:
> On Thu, Dec 4, 2008 at 2:40 PM, Jarrod Millman
> <[EMAIL PROTECTED]> wrote:
>> On Thu, Dec 4, 2008 at 11:14 AM, Pierre GM <[EMAIL PROTECTED]>
>> wrote:
>>> Raise a ValueError (even in 2.5, therefore risking to break
>>> something)
>>
>>
On Thu, Dec 4, 2008 at 2:40 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 4, 2008 at 11:14 AM, Pierre GM <[EMAIL PROTECTED]> wrote:
>> Raise a ValueError (even in 2.5, therefore risking to break something)
>
> +1
>
+1
I'm not yet a serious user of numpy/scipy, but when debugging the
On Thu, Dec 4, 2008 at 11:14 AM, Pierre GM <[EMAIL PROTECTED]> wrote:
> Raise a ValueError (even in 2.5, therefore risking to break something)
+1
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
_
On Nov 25, 2008, at 12:23 PM, Pierre GM wrote:
> All,
> Sorry to bump my own post, and I was kinda threadjacking anyway:
>
> Some functions of numy.ma (eg, ma.max, ma.min...) accept explicit
> outputs that may not be MaskedArrays.
> When such an explicit output is not a MaskedArray, a value tha
All,
Sorry to bump my own post, and I was kinda threadjacking anyway:
Some functions of numy.ma (eg, ma.max, ma.min...) accept explicit
outputs that may not be MaskedArrays.
When such an explicit output is not a MaskedArray, a value that should
have been masked is transformed into np.nan.
Tha
