[Numpy-discussion] nasty bug in 1.8.0??
nouiz at nouiz.org
Mon Dec 2 14:19:07 EST 2013
There is a way to compile NumPy to use strange strides for dimension
with shape of 1.
This is done to help developer test their code to don't rely on this.
There was never a warranty to the value of strides in that cases. Most
of the time, it was the same, but in some cases, it was different.
Using such strange strides will cause segfault if you use them, so it
allow to see if you rely on them.
In Theano, we did some assertion on strides and checked them for
optimized call to blas. So we will need to change some code to support
But I don't those strange strides should happen in the wild. Did you
installed NumPy manually?
On Mon, Dec 2, 2013 at 2:14 PM, Daπid <davidmenhur at gmail.com> wrote:
> I get:
> In : x.strides
> Out: (8,)
> Same architecture and OS, Numpy installed via Pip on Python 2.7.5.
> On 2 December 2013 20:08, Neal Becker <ndbecker2 at gmail.com> wrote:
>> This is np 1.8.0 on fedora x86_64:
>> In : x =np.array ((1,))
>> In : x.shape
>> Out: (1,)
>> In : x.strides
>> Out: (9223372036854775807,)
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
More information about the NumPy-Discussion