[Numpy-discussion] Time for beta1 of NumPy 1.0 (original) (raw)

Sasha ndarray at mac.com
Thu Jun 29 22:38:21 EDT 2006

I vote for no change. It will be a major backward compatibility headache with applications that rely on integer arrays breaking in mysterious ways. If float wins, I hope there will be a script to update old code. Detecting single argument calls to these functions is probably not very hard.

On 6/29/06, Keith Goodman <kwgoodman at gmail.com> wrote:

On 6/29/06, Alan G Isaac <aisaac at american.edu> wrote: > On Thu, 29 Jun 2006, Travis Oliphant apparently wrote: > > Please make any comments or voice major concerns > > A rather minor issue, but I would just like to make sure > that a policy decision was made not to move to a float > default for identity(), ones(), zeros(), and empty(). > (I leave aside arange().) > > I see the argument for a change to be 3-fold: > 1. It is easier to introduce people to numpy if > default data types are all float. (I teach, > and I want my students to use numpy.) > 2. It is a better match to languages from which > users are likely to migrate (e.g., GAUSS or > Matlab). > 3. In the uses I am most familiar with, float is > the most frequently desired data type. (I guess > this may be field specific, especially for empty().)

I vote float. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Numpy-discussion mailing list Numpy-discussion at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion

More information about the NumPy-Discussion mailing list