On Tue, Apr 1, 2014 at 1:12 PM, Nathaniel Smith <n...@pobox.com> wrote:
> In [6]: a[0] = "garbage" > ValueError: could not convert string to float: garbage > > (Cf, "Errors should never pass silently".) Any reason why datetime64 > should be different? > datetime64 is different because it has NaT support from the start. NaN support for floats seems to be an afterthought if not an accident of implementation. And it looks like some errors do pass silently: >>> a[0] = "1" # not a TypeError But I withdraw my suggestion. The closer datetime64 behavior is to numeric types the better.
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
