Re: [Numpy-discussion] Altering/initializing NumPy array in C

2014-01-02 Thread Bart Baker
> You're stack-allocating your array, so the memory is getting recycled for > other uses as soon as your C function returns. You should malloc it instead > (but you don't have to worry about free'ing it, numpy will do that when the > array object is deconstructed). Any C reference will fill you in

Re: [Numpy-discussion] Altering/initializing NumPy array in C

2014-01-01 Thread Nathaniel Smith
On 1 Jan 2014 13:57, "Bart Baker" wrote: > > Hello, > > I'm having issues with performing operations on an array in C and > passing it back to Python. The array values seem to become unitialized > upon being passed back to Python. My first attempt involved initializing > the array in C as so: > >

[Numpy-discussion] Altering/initializing NumPy array in C

2014-01-01 Thread Bart Baker
Hello, I'm having issues with performing operations on an array in C and passing it back to Python. The array values seem to become unitialized upon being passed back to Python. My first attempt involved initializing the array in C as so: double a_fin[max_mth]; where max_mth is an int. I fill in