[Numpy-discussion] @Dag re numpy.pxd

Dag Sverre Seljebotn d.s.seljebotn@astro.uio...
Tue Feb 14 08:50:13 CST 2012

On 02/14/2012 06:22 AM, Gordon L. Kindlmann wrote:
> Hello,
> This (below) caught my eye and I'm wondering what further information is available?
> I very much value the ability to wrap underlying array data from numpy for processing in non-python libraries, as well as the ability to wrap numpy arrays around array data allocated by non-python libraries.
> Is this capability going to be removed?

This discussion had nothing to do with what you are saying above.


> Gordon
>> Message: 6
>> Date: Sat, 11 Feb 2012 13:31:51 -0700
>> From: Charles R Harris<charlesr.harris@gmail.com>
>> Subject: [Numpy-discussion] @Dag re numpy.pxd
>> To: numpy-discussion<numpy-discussion@scipy.org>
>> Message-ID:
>> 	<CAB6mnxJVERqK64UpG3GOmaWDQHUn-z-=WJMQju0iU4KO9sefTg@mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>> Hi Dag,
>> This probably needs to be on the cython mailing list at some point, but I
>> thought I'd start the discussion here. Numpy is going to begin deprecating
>> direct access to ndarray/dtype internals, ala arr->data etc. There are
>> currently macros/functions for many of these operations in the numpy
>> development branch and I expect more to go in over the coming year. Also,
>> some of the macros have been renamed. I don't know the best way for Cython
>> to support this, but the current version (0.15 here) generates code that
>> will fail if the deprecated things are excluded. Ideally, numpy.pxd would
>> have numpy version dependent parts but I don't know if that is possible. In
>> any case, I'd like your thoughts on the best way to coordinate this
>> migration with Cython.
>> Chuck
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion

More information about the NumPy-Discussion mailing list