[Numpy-discussion] Time for beta1 of NumPy 1.0

Stephan Tolksdorf st at sigmasquared.net
Fri Jun 30 02:53:30 EDT 2006

I guess this is a change which would just break too much code. And if 
the default type should by changed for these functions, why not also for 
  array constructors?

On the other hand, many people probably use Numpy almost exclusively 
with Float64's. A convenient way to change the default type could make 
their code easier to read.
How much effort would it be to provide a convenience module that after 
importing replaces the relevant functions with wrappers that make 
Float64's the default?


Alan G Isaac 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().)
> Cheers,
> Alan Isaac

More information about the NumPy-Discussion mailing list