[Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

Charles R Harris charlesr.harris@gmail....
Tue Oct 2 12:18:24 CDT 2012


On Tue, Oct 2, 2012 at 9:45 AM, Frédéric Bastien <nouiz@nouiz.org> wrote:

> We implement our own subtensor(x[...], where ... can be index or
> slice) c code due to the way Theano work.
>
> I can probably change the logic, but if you plan to revert this
> interface changes, I prefer to wait for this change we someone else is
> doing other changes that would conflict. Also, I did a Theano release
> candidate and I really would like the final version to work with the
> next release of NumPy.
>

Well, you don't *have* to define NPY_NO_DEPRECATED_API. If you don't you
can access the array as before using the macros even for future versions of
numpy. The only way that could cause a problems is if the array structure
is rearranged and I don't think that will happen anytime soon. On that
account there has not been any discussion of reverting the changes.
However, I'd like f2py generated modules to use the new functions at some
point and in order to do that numpy needs to supply some extra
functionality, I'm just not sure of the best way to do it at the moment. If
I had a good idea of what you want to do it would help in deciding what
numpy should provide.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20121002/ba5c4c5e/attachment.html 


More information about the NumPy-Discussion mailing list