[Numpy-discussion] Time for beta1 of NumPy 1.0 (original) (raw)
Bill Baxter wbaxter at gmail.com
Thu Jun 29 22:40:19 EDT 2006
- Previous message (by thread): [Numpy-discussion] Time for beta1 of NumPy 1.0
- Next message (by thread): [Numpy-discussion] Time for beta1 of NumPy 1.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I also find the int behavior of these functions strange.
+1 float default (or double)
--bb
On 6/30/06, Tim Leslie <tim.leslie at gmail.com> wrote:
On 6/30/06, Keith Goodman <kwgoodman at gmail.com> wrote: > On 6/29/06, Alan G Isaac <aisaac at american.edu> wrote: > > 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. +1 float Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20060630/990cc872/attachment.html>
- Previous message (by thread): [Numpy-discussion] Time for beta1 of NumPy 1.0
- Next message (by thread): [Numpy-discussion] Time for beta1 of NumPy 1.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]