On Fri, 30 Jun 2006, Jonathan Taylor apparently wrote:
> In general though I agree that this is a now or never change.
Sasha has also made that argument.
I see one possible additional strategy.
I think every agrees that the long view is important.
Now even Sasha agrees that float64 is the best default.
Suppose
1. float64 is the ideal default (I agree with this)
2. there is substantial concern about the change of
default on extant code for the unwary
One approach proposed is to include a different function
definition in a compatability module. This seems acceptable
to me, but as Sasha notes it is not without drawbacks.
Here is another possibility:
transition by requiring an explicit data type for some
period of time (say, 6-12 months). After that time,
provide the default of float64. This would require
some short term pain, but for the long term gain of
the desired outcome.
Just a thought,
Alan Isaac
PS I agree with Sasha's following observations:
"arrays other than float64 are more of the hard-hat area and
their properties may be surprising to the novices. Exposing novices
to non-float64 arrays through default constructors is a bad thing.
...
No one expects that their Numeric or numarray code
will work in numpy 1.0 without changes, but I don't think people will
tolerate major breaks in backward compatibility in the future
releases.
...
If we decide to change the default, let's do it everywhere including
array constructors and arange."
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion
