> If your arrays are contiguous, you don't really need the strides (use the
itemsize instead). How is ndarray broken by this?
ndarray is broken by this change because it expects the stride to be a
multiple of the itemsize (I think; I'm just looking at code here, as I
haven't had time to build NumP
fer interface), there's no longer any way for a NumPy array to
hold data allocated by something other than NumPy.
If I want to put external memory in a NumPy array and indicate that it's
owned by some non-NumPy Python object, what is the recommended way to do
that?
Thanks!
Jim Bosc
On 05/11/2012 01:36 AM, Travis Oliphant wrote:
>>>
>>> I guess this mixture of Python-API and C-API is different from the way
>>> the API tries to protect incorrect access. From the Python API, it.
>>> should let everything through, because it's for Python code to use. From
>>> the C API, it should
l of the above does work on a number of other systems, so I suspect
something went wrong with this particular NumPy install, but it claims
to have been successful. This is with gcc 4.1.2, RHEL 5. Any ideas?
Thanks!
Jim Bosch
___
NumPy-Discussion mailing li
On 04/03/2012 12:48 PM, Chris Barker wrote:
> On Tue, Apr 3, 2012 at 6:06 AM, Holger Herrlich
>
>> I know of
>> boost.python so far.
>
> I've never used boost.python, but it's always seemed to me to be kind
> of heavy weight and not all that well maintained [1]
>
> -- but don't take my word for
