On Fri, Jul 1, 2011 at 6:01 AM, Neal Becker wrote:
> Just trying it out with 1.6:
>
> np.datetime64('now')
> Out[6]: 2011-07-01 00:00:00
>
> Well the time now is 07:01am. Is this expected behaviour?
>
The version of datetime in 1.6 is quite broken. When 1.6 was released, I
thought it was proba
On Fri, Jul 1, 2011 at 5:01 AM, Neal Becker wrote:
> Just trying it out with 1.6:
>
> np.datetime64('now')
> Out[6]: 2011-07-01 00:00:00
>
> I get
In [1]: datetime64('now')
Out[1]: numpy.datetime64('2011-07-01T07:18:35-0600')
You need the development branch for trials, Mark has made a lot of
f
Just trying it out with 1.6:
np.datetime64('now')
Out[6]: 2011-07-01 00:00:00
Well the time now is 07:01am. Is this expected behaviour?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussi
https://github.com/numpy/numpy/pull/101
Thanks,
Mark
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion