On Wed, Jan 6, 2016 at 8:30 AM, Ralf Gommers wrote:
>
>
>
> On Mon, Jan 4, 2016 at 9:38 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>>
>>
>> The failed tests require pyrex, fortran, and swig. The refcount error
>> comes and goes, probably the test isn't very good. Ralf, is there a
On Mon, Jan 4, 2016 at 9:38 PM, Charles R Harris
wrote:
>
>
> The failed tests require pyrex, fortran, and swig. The refcount error
> comes and goes, probably the test isn't very good. Ralf, is there any
> reason to keep the various extension building tests? They are very old.
>
There are f2py t
On Sat, Jan 2, 2016 at 10:05 PM, wrote:
> On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
> wrote:
> > Hi All,
> >
> > A significant segfault problem has been reported against Numpy 1.10.2
> and I
> > want to make a quick 1.10.3 release to get it fixed. Two questions
> >
> > What exactly is the
On Sun, Jan 3, 2016 at 12:05 AM, wrote:
> On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
> wrote:
>> Hi All,
>>
>> A significant segfault problem has been reported against Numpy 1.10.2 and I
>> want to make a quick 1.10.3 release to get it fixed. Two questions
>>
>> What exactly is the release
On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
wrote:
> Hi All,
>
> A significant segfault problem has been reported against Numpy 1.10.2 and I
> want to make a quick 1.10.3 release to get it fixed. Two questions
>
> What exactly is the release process that has been decided on? AFAIK, I
> should
On Sun, Jan 3, 2016 at 12:01 AM, Charles R Harris
wrote:
>
>
> On Sat, Jan 2, 2016 at 4:51 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
>> wrote:
>> > Hi All,
>> >
>> > A significant segfault problem has been reported against Numpy 1.10.2
>> > and I
On Sat, Jan 2, 2016 at 4:51 PM, Matthew Brett
wrote:
> Hi,
>
> On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
> wrote:
> > Hi All,
> >
> > A significant segfault problem has been reported against Numpy 1.10.2
> and I
> > want to make a quick 1.10.3 release to get it fixed. Two questions
> >
>
Hi,
On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
wrote:
> Hi All,
>
> A significant segfault problem has been reported against Numpy 1.10.2 and I
> want to make a quick 1.10.3 release to get it fixed. Two questions
>
> What exactly is the release process that has been decided on? AFAIK, I
> s