On Thu, May 22, 2008 at 4:25 PM, Bruce Southey <[EMAIL PROTECTED]> wrote: > On Thu, May 22, 2008 at 2:59 PM, Robert Kern <[EMAIL PROTECTED]> wrote: >> On Thu, May 22, 2008 at 2:46 PM, Charles R Harris >> <[EMAIL PROTECTED]> wrote: >>> It also leads to various inconsistencies: >>> >>> In [1]: float32(array([[1]])) >>> Out[1]: array([[ 1.]], dtype=float32) >>> >>> In [2]: float64(array([[1]])) >>> Out[2]: 1.0 >> >> Okay, so don't do that. Always use x.astype(dtype) or asarray(x, dtype). > > So, should these return an error if the argument is an ndarray object, > a list or similar?
I think it was originally put in as a feature, but given the inconsistency and the long-standing alternatives, I would deprecate its use for converting array dtypes. But that's just my opinion. > Otherwise, int, float and string type of arguments would be okay under > the assumption that people would like variable precision scalars. Yes. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ Numpy-discussion mailing list [email protected] http://projects.scipy.org/mailman/listinfo/numpy-discussion
