[Numpy-discussion] datetime64 y2k38 bug
Charles R Harris
Sun Sep 18 22:08:49 CDT 2011
On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root <firstname.lastname@example.org> wrote:
> I was working on adding some test cases in numpy for the argmin/max
> functions with some datetime64s. I found that on my 32-bit machine, it
> fails to parse a date past the Y2.038k date. I find this odd because the
> datetime is supposed to be 64-bits, but I guess there is some arch-dependent
> code somewhere?
I think that is actually POSIX for the time_t structure. Which is not to say
it's good ;) Google UNIX Year 2038 problem. ISTR reading recently that there
is a movement afoot to fix the time_t structure on 32 bit machines for
Linux. You've got to wonder, what were the POSIX people thinking?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion