On 4/22/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Bill Baxter wrote:
> > What's the right way to make a new numpy array that's a copy of some C data?
> >
> What do you mean by /copies/ the void * data pointer for you? Do you
> mean the API would
>
> 1) Create new memory for the array
> 2)
On 4/21/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Bill Baxter wrote:
> > What's the right way to make a new numpy array that's a copy of some C data?
> >
> > There doesn't seem to be any API like PyArray_NewFromDescr that
> > /copies/ the void*data pointer for you. Do I have to write my own
Bill Baxter wrote:
> What's the right way to make a new numpy array that's a copy of some C data?
>
> There doesn't seem to be any API like PyArray_NewFromDescr that
> /copies/ the void*data pointer for you. Do I have to write my own
> loops for this? I can do that, it just seems like it should b
Anton Sherwood wrote (Apr 11):
>> When I try to build numpy (or PIL) on MacOS, I get this error:
>> "gcc: cannot specify -o with -c or -S and multiple compilations"
>>
>> Assuming at least one of you is using numpy on MacOS,
>> how did you get around that?
Christopher Barker wrote:
> by inst
On 4/19/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> What's the right way to make a new numpy array that's a copy of some C data?
>
> There doesn't seem to be any API like PyArray_NewFromDescr that
> /copies/ the void*data pointer for you. Do I have to write my own
> loops for this? I can do that
Yes,
that worked - many thanks!
Christian.
On Thu, April 19, 2007 22:38, David M. Cooke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Christian Marquardt wrote:
>> Dear David,
>>
>> the svn version of numpy does indeed build cleanly on AIX. Many thanks!
>>
>> However, the wrapp
