Issue 762920: API Functions for PyArray (original) (raw)

Created on 2003-06-29 23:48 by kohanman, last changed 2022-04-10 16:09 by admin. This issue is now closed.

Messages (7)
msg44141 - (view)	Author: Ralph (kohanman)	Date: 2003-06-29 23:48
I'd rather send and recieve PyArrays into my C modules since I often end up with a foo(int count, type *data) call anyway. Sure, there's NumPy for this sort of dirtywork, but this is so much more convienient.
msg44142 - (view)	Author: Raymond Hettinger (rhettinger) *	Date: 2007-04-03 02:55
This proposal is basically fine. It will need docs and it can go into Py2.6.
msg64406 - (view)	Author: Raymond Hettinger (rhettinger) *	Date: 2008-03-24 09:04
Raising priority as a reminder to myself or anyone who wants to apply, test, and document.
msg64454 - (view)	Author: Alexander Belopolsky (belopolsky) *	Date: 2008-03-25 03:11
I think this issue is largely superseded by PEP 3118 <http://www.python.org/dev/peps/pep-3118>, which is being backported to 2.6 (see ). AFAICT, the only functionality not available from the new buffer protocol is the ability to create new array objects from C code, but this patch does not provide such functionality either. Travis, can you weigh in on this? I think it may be useful to expose newarrayobject() through some C API compatible with PEP 3118, but otherwise this proposal seems redundant.
msg67978 - (view)	Author: Travis Oliphant (teoliphant) *	Date: 2008-06-11 14:22
I will look at the patch, but generally I'm not inclined to give the array module more legs because I agree that the desired functionality should be put into the memoryview object and the buffer protocol.
msg106638 - (view)	Author: Alexander Belopolsky (belopolsky) *	Date: 2010-05-28 05:25
Is there still any interest in pursuing this? Raymond?
msg114248 - (view)	Author: Mark Lawrence (BreamoreBoy) *	Date: 2010-08-18 16:42
Closed as no reply to .