[Numpy-discussion] segfaulting numpy with dot and datetime

josef.pktd@gmai... josef.pktd@gmai...
Mon Dec 10 20:46:29 CST 2012


On Mon, Dec 10, 2012 at 8:54 PM,  <josef.pktd@gmail.com> wrote:
> On Mon, Dec 10, 2012 at 8:26 PM, Charles R Harris
> <charlesr.harris@gmail.com> wrote:
>>
>> On Mon, Dec 10, 2012 at 5:39 PM, <josef.pktd@gmail.com> wrote:
>>>
>>> >>> np.__version__
>>> '1.6.2'
>>> >>> aa
>>> array([1970-01-13 96:00:00, 1970-01-13 120:00:00, 1970-01-13 144:00:00,
>>>        1970-01-13 168:00:00, 1970-01-13 192:00:00], dtype=datetime64[ns])
>>> >>> np.dot(aa, [1])
>>> <segfault>
>>>
>>
>> Hmm, I can't even get that array using current master, what with illegal
>> hours and all. Datetime in 1.6.x wasn't quite up to snuff, so things might
>> have been fixed in 1.7.0. Is there any way you can check that.
>
> I didn't know the dates are illegal, they were created with pandas.

here's the minimal numpy version

>>> np.ones(5, 'datetime64[ns]')
array([1970-01-01 00:00:00, 1970-01-01 00:00:00, 1970-01-01 00:00:00,
       1970-01-01 00:00:00, 1970-01-01 00:00:00], dtype=datetime64[ns])
>>> b = np.ones(5, 'datetime64[ns]')
>>> np.dot(b, [1])
<segfault>

virtualenv is next

Josef

>
> Skipper said he couldn't replicate the segfault so it might be gone
> with a more recent numpy.
> I still have to setup a virtualenv for a 1.7.0 beta so I can start to test it.
> (I rely on binaries for numpy and scipy now.)
>
> Thanks,
>
> Josef
>
>>
>> Chuck
>>
>>
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>


More information about the NumPy-Discussion mailing list