Re: [Numpy-discussion] vectorize pitfall

2006-10-25 Thread A. M. Archibald
On 25/10/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > It takes old "type-codes" as one big string so you say > > vectorize(f,otypes='d') > > This should be modernized to handle a list of dtype objects. > > I've fixed vectorize in SVN. Thanks! A. M. Archibald

Re: [Numpy-discussion] vectorize pitfall

2006-10-25 Thread Travis Oliphant
A. M. Archibald wrote: > Hi, > > Vectorize is a very handy function, but it has at least one pitfall: > > def f(x): > if 1.3 return sqrt(x) > else: > return 0 > > Now vectorize(f)(2)=1.41421356237 but vectorize(f)(array([1,2]))=array([0,1]). > > The problem is that, when giv

[Numpy-discussion] vectorize pitfall

2006-10-25 Thread A. M. Archibald
Hi, Vectorize is a very handy function, but it has at least one pitfall: def f(x): if 1.3http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.