[Numpy-discussion] Time for beta1 of NumPy 1.0 (original) (raw)
Alan G Isaac aisaac at american.edu
Fri Jun 30 15:02:47 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 ]
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
- float64 is the ideal default (I agree with this)
- 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."
- 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 ]