I agree with that interpretation of naive as well. I'll change the proposal to reflect that. So any modifier should raise an error then? (At the risk of breaking people's code.)
The only question is, should we consider accepting the modifier and disregard it with a warning, letting the user know that this is only for temporary compatibility purposes? As of now, it's not clear to me which of those options is better. Cheers, Sankarshan On Apr 1, 2014, at 1:12 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Tue, Apr 1, 2014 at 5:22 PM, Alexander Belopolsky <ndar...@mac.com> wrote: >> >> On Tue, Apr 1, 2014 at 12:10 PM, Chris Barker <chris.bar...@noaa.gov> wrote: >>> >>> It seems this committee of two has come to a consensus on naive -- and >>> you're probably right, raise an exception if there is a time zone specifier. >> >> >> Count me as +1 on naive, but consider converting garbage (including strings >> with trailing Z) to NaT. > > That's not how we handle other types, e.g.: > > In [5]: a = np.zeros(1, dtype=float) > > 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? > > -n > > -- > Nathaniel J. Smith > Postdoctoral researcher - Informatics - University of Edinburgh > http://vorpus.org > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Sankarshan Mudkavi Undergraduate in Physics, University of Waterloo www.smudkavi.com
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
