fullung at gmail.com
Fri Mar 31 04:24:05 CST 2006
I've noticed a lot of fixes going into NumPy during the past couple of weeks
and I'm very excited about the progress that is being made.
However, it seems many changes are being made without the addition of test
cases to make sure that things don't break again in the future. The code
snippet Tim provided to reproduce the bug mentioned below would be a perfect
test, but it doesn't seem as if a test for this bug was added in the
changeset where the bug was fixed or any changeset since.
> -----Original Message-----
> From: numpy-discussion-admin at lists.sourceforge.net [mailto:numpy-
> discussion-admin at lists.sourceforge.net] On Behalf Of Sasha
> Sent: 31 March 2006 07:20
> To: tim.hochberg at ieee.org
> Cc: numpy-discussion
> Subject: Re: [Numpy-discussion] Segfault!
> Fixed. <http://projects.scipy.org/scipy/numpy/changeset/2312>
> On 3/30/06, Tim Hochberg <tim.hochberg at cox.net> wrote:
> > The following snippet utilizing a rank-0 array will segfault numpy:
> > import numpy
> > a = numpy.array(4)
> > b = numpy.arange(10)
> > a *= b
> > (Build '0.9.7.2301' using VC7 on windows).
> > I'll file a better bug report tomorrow, assuming this hasn't been fixed,
> > but I'm on my way out the door.
> > -tim
More information about the Numpy-discussion