2008/4/23 Travis E. Oliphant <[EMAIL PROTECTED]>:
> I'm curious who made the change and why. There was code intentionally
> there to interpret None as nan for float arrays. So, I don't
> understand why and/or when it changed.
I find that behaviour counterintuitive (I'm not the one who changed i
On Tue, Apr 22, 2008 at 5:51 PM, Charles R Harris <[EMAIL PROTECTED]>
wrote:
>
>
> On Tue, Apr 22, 2008 at 4:00 PM, Travis E. Oliphant <
> [EMAIL PROTECTED]> wrote:
>
> > Stéfan van der Walt wrote:
> > > 2008/4/22 lorenzo bolla <[EMAIL PROTECTED]>:
> > >
> > >> I noticed a change in the behaviour
On Tue, Apr 22, 2008 at 4:00 PM, Travis E. Oliphant <[EMAIL PROTECTED]>
wrote:
> Stéfan van der Walt wrote:
> > 2008/4/22 lorenzo bolla <[EMAIL PROTECTED]>:
> >
> >> I noticed a change in the behaviour of numpy.asfarray between numpy
> version
> >> 1.0.5 and 1.1.0:
> >>
> >> 1.0.5
> >>
> >>
>
Stéfan van der Walt wrote:
> 2008/4/22 lorenzo bolla <[EMAIL PROTECTED]>:
>
>> I noticed a change in the behaviour of numpy.asfarray between numpy version
>> 1.0.5 and 1.1.0:
>>
>> 1.0.5
>>
>>
>> In [3]: numpy.asfarray(None)
>> Out[3]: array(nan)
>> In [4]: numpy.__version__
>> Out[4]: '1.0
2008/4/22 lorenzo bolla <[EMAIL PROTECTED]>:
> I noticed a change in the behaviour of numpy.asfarray between numpy version
> 1.0.5 and 1.1.0:
>
> 1.0.5
>
>
> In [3]: numpy.asfarray(None)
> Out[3]: array(nan)
> In [4]: numpy.__version__
> Out[4]: '1.0.5.dev4455'
>
> 1.1.0
>
>
> In [16]: nu
I noticed a change in the behaviour of numpy.asfarray between numpy version
1.0.5 and 1.1.0:
1.0.5
In [3]: numpy.asfarray(None)
Out[3]: array(nan)
In [4]: numpy.__version__
Out[4]: '1.0.5.dev4455'
1.1.0
In [16]: numpy.asfarray(None)
