Eric Firing wrote:
>Pierre GM wrote:
>
>
>>All,
>>I've updated this famous reimplementation of maskedarray I keep ranting about.
>>
>>
>[...]
>
>
>>I also put the file `timer_comparison.py`, that runs some unittests with each
>>implementation
>>(numpy.core.ma and maskedarray), and outputs
Pierre GM wrote:
> All,
> I've updated this famous reimplementation of maskedarray I keep ranting about.
[...]
> I also put the file `timer_comparison.py`, that runs some unittests with each
> implementation
> (numpy.core.ma and maskedarray), and outputs the minimum times.
> On my machine, there d
Robert Kern wrote:
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>>
>> which I cannot parse. Any ideas?
>
> Possibly you are linking against the wrong wx libraries.
It's worth a try, but that doesn't look familiar.
New MPL binaries have been put up on pythonmac.org/packages.
I'm
Hi,
ProStr = N.rec.array(None,
formats="u4,f4,u4,u4,4u4",
names=('count','clock','InitDio',
'nDigital', 'nAnalog'),
aligned=True, shape=1)
ProStr[0] ['nAnalog'] = 1
I
josh kantor wrote:
>I am working on a project where I am doing some interfacing with numpy
>arrays at a C level.
>
>One thing that I want to do (using pyrex) is to call numpy functions, then
>directly access the underlying double * array of the resulting ndarray and
>operate on it in C/pyrex (I
El dc 17 de 01 del 2007 a les 03:54 -0700, en/na josh kantor va
escriure:
> I am working on a project where I am doing some interfacing with numpy
> arrays at a C level.
>
> One thing that I want to do (using pyrex) is to call numpy functions, then
> directly access the underlying double * array
I am working on a project where I am doing some interfacing with numpy
arrays at a C level.
One thing that I want to do (using pyrex) is to call numpy functions, then
directly access the underlying double * array of the resulting ndarray and
operate on it in C/pyrex (I don't want to copy it). I
