On Sun, Sep 18, 2011 at 8:52 PM, wrote:
> On Sun, Sep 18, 2011 at 11:13 PM, Charles R Harris
> wrote:
> >
> >
> > On Sun, Sep 18, 2011 at 9:08 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root wrote:
> >>>
> >>> I was working on adding some test case
On Sun, Sep 18, 2011 at 11:13 PM, Charles R Harris
wrote:
>
>
> On Sun, Sep 18, 2011 at 9:08 PM, Charles R Harris
> wrote:
>>
>>
>> On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root wrote:
>>>
>>> I was working on adding some test cases in numpy for the argmin/max
>>> functions with some datetime64
On Sunday, September 18, 2011, Charles R Harris
wrote:
>
>
> On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root 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.03
On Sun, Sep 18, 2011 at 9:08 PM, Charles R Harris wrote:
>
>
> On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root 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 t
On Sun, Sep 18, 2011 at 6:32 PM, Benjamin Root 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
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 som
