Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-09 Thread Charles R Harris
On Sun, Sep 9, 2012 at 1:42 PM, Charles R Harris wrote: > > > On Sun, Sep 9, 2012 at 11:12 AM, Frédéric Bastien wrote: > >> Hi, >> >> On Thu, Sep 6, 2012 at 11:32 AM, Charles R Harris >> wrote: >> > >> > >> > On Thu, Sep 6, 2012 at 10:07 AM, Frédéric Bastien >> wrote: >> >> >> >> Hi, >> >> >> >

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-09 Thread Charles R Harris
On Sun, Sep 9, 2012 at 11:12 AM, Frédéric Bastien wrote: > Hi, > > On Thu, Sep 6, 2012 at 11:32 AM, Charles R Harris > wrote: > > > > > > On Thu, Sep 6, 2012 at 10:07 AM, Frédéric Bastien > wrote: > >> > >> Hi, > >> > >> I reply with more information probably later today or tomorrow, but I > >>

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-09 Thread Frédéric Bastien
Hi, On Thu, Sep 6, 2012 at 11:32 AM, Charles R Harris wrote: > > > On Thu, Sep 6, 2012 at 10:07 AM, Frédéric Bastien wrote: >> >> Hi, >> >> I reply with more information probably later today or tomorrow, but I >> think i need to finish everything to give you the exact information. >> >> Part of

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-06 Thread Matthew Brett
Hi, On Wed, Sep 5, 2012 at 7:05 PM, David Cournapeau wrote: > Hi Frederic, > > On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien wrote: >> Hi, >> >> I spent up to now 2 or 3 days making change to Theano to support numpy >> 1.7b1. But now, I just find an interface change that will need >> recoding

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-06 Thread Charles R Harris
On Thu, Sep 6, 2012 at 10:07 AM, Frédéric Bastien wrote: > Hi, > > I reply with more information probably later today or tomorrow, but I > think i need to finish everything to give you the exact information. > > Part of the problem I had was that by default there is a warning that > is generated.

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-06 Thread Frédéric Bastien
Hi, I reply with more information probably later today or tomorrow, but I think i need to finish everything to give you the exact information. Part of the problem I had was that by default there is a warning that is generated. It tell that to remove this warning we need to set NPY_NO_DEPRECATED_A

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Ondřej Čertík
Hi Fred, On Wed, Sep 5, 2012 at 10:56 AM, Nathaniel Smith wrote: > On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien wrote: >> Hi, >> >> I spent up to now 2 or 3 days making change to Theano to support numpy >> 1.7b1. But now, I just find an interface change that will need >> recoding a function,

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread David Cournapeau
Hi Frederic, On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien wrote: > Hi, > > I spent up to now 2 or 3 days making change to Theano to support numpy > 1.7b1. But now, I just find an interface change that will need > recoding a function, not just small code change. > > The problem is that we can'

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Nathaniel Smith
On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien wrote: > Hi, > > I spent up to now 2 or 3 days making change to Theano to support numpy > 1.7b1. But now, I just find an interface change that will need > recoding a function, not just small code change. My understanding was that 1.7 is not suppose

[Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Frédéric Bastien
Hi, I spent up to now 2 or 3 days making change to Theano to support numpy 1.7b1. But now, I just find an interface change that will need recoding a function, not just small code change. The problem is that we can't access fields from PyArrayObject anymore, we absolutely must use the old macro/ne