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_API=NPY_1_7_API_VERSION. I didn't saw it before my first email, but some code I didn't wrote was passing the -Werror flag to g++, so this created errors for me. At first, I added this macro, but this caused error because we used the old C-API. I'm gatering all the correct information/comments and reply later with them. Fred On Wed, Sep 5, 2012 at 6:03 PM, Ondřej Čertík <ondrej.certik@gmail.com> wrote:
Hi Fred,
On Wed, Sep 5, 2012 at 10:56 AM, Nathaniel Smith <njs@pobox.com> wrote:
On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien <nouiz@nouiz.org> 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 supposed to require any code changes... so, separate from your actual question about assigning to the data field can I ask: are the changes you're talking about just to avoid *deprecated* APIs, or did you have actual problems running Theano against 1.7b1? And if you had actual problems, could you say what? (Or just post a diff of the changes you found you had to make, which should amount to the same thing?)
Thank you for trying the beta version, that was the purpose to put it out there and see if it breaks things.
As others said, if you can give us more details, that'd be great. Let's get it fixed before rc1.
Ondrej _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion