Le Mardi 8 Août 2006 05:18, Bill Baxter a écrit :
> I see Pyrex and SWIG examples in numpy/doc but there doesn't seem to be an
> example of just a simple straightforward usage of the C-API.
> For instance make a few arrays by hand in C and then call numpy.multiply()
> on them. So far my attempts t
I started to do the same with array methods, but before I spend too much time on it, I'd like to be sure I'm doing the right thing.1. In add_newdocs.py, add from numpy.core import ndarray2. then add an entry for each method, eg
add_docstring(ndarray.var, """a.var(axis=None, dtype=None) Retur
Hi,
we are using numerical python as an integral part of a microscope
development project over last few years.
So far we have been using exclusively numarray but now I decided it's
time to slowly but sure migrate to numpy.
What is the proper way to reference these packages ?
Thanks to everyone
Hi!
I have a problem with record array type descriptor.
With numarray this used to work.
My records made of n integers and m floats. So I used to be able specify
formats="%di4,%df4"%(self.numInts,self.numFloats) in numarray which would
translate to
byteorder = self.isByteSwapped and '>' or '<'
Matthew Brett wrote:
> Hi,
>
> Sorry if this is silly question, but should this work to convert from
> int8 to character type?
>
> a = array([104, 105], dtype=N.int8)
> a.astype('|S1')
>
I'm not sure what you are trying to do here, but the standard coercion
to strings will generate
['104', '105
Sebastian Haase wrote:
> Hi!
> I have a problem with record array type descriptor.
> With numarray this used to work.
> My records made of n integers and m floats. So I used to be able specify
> formats="%di4,%df4"%(self.numInts,self.numFloats) in numarray which would
> translate to
> byteorder
On Wednesday 09 August 2006 15:18, Travis Oliphant wrote:
> Sebastian Haase wrote:
> > Hi!
> > I have a problem with record array type descriptor.
> > With numarray this used to work.
> > My records made of n integers and m floats. So I used to be able
> > specify formats="%di4,%df4"%(self.numInt
It seems that this old problem of compiling Numeric is a problem again
(even on my Linux box, not just cygwin):
http://sourceforge.net/tracker/index.php?func=detail&aid=732520&group_id=1369&atid=301369
(The issue was the dlamch.f code)
The patch recommended to run:
python setup.py config
i
Jim Kleckner wrote:
> It seems that this old problem of compiling Numeric is a problem again
> (even on my Linux box, not just cygwin):
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=732520&group_id=1369&atid=301369
>
>
>
> (The issue was the dlamch.f code)
>
> The patch recommen
Travis Oliphant wrote:
> Sebastian Haase wrote:
>> On Wednesday 09 August 2006 15:45, you wrote:
>>
>>> Sebastian Haase wrote:
>>>
On Wednesday 09 August 2006 15:18, Travis Oliphant wrote:
> If numarray supported it, then we should get NumPy to support it as
> well
>>
Hi,
we are using numerical python as an integral part of a microscope
development project over last few years.
So far we have been using exclusively numarray but now I decided it's
time to slowly but sure migrate to numpy.
What is the proper way to reference these packages ?
Thanks to everyone i
P. F. Dubois, K. Hinsen, and J. Hugunin, "Numerical Python", Computers
in Physics, v. 10, #3, May/June 1996.
is one reference people have used. Others simply refer to the website.
The new book might be the best for numpy itself, dunno.
Related papers are:
David Ascher, P. F. Dubois, Konrad Hinse
Hello,
I recently switched from a Debian Linux box to a Mac G5
PowerPC, running Mac OS X 10.4 Tiger (8.7.0). I use the
Python Numeric package extensively, and have come to
depend upon it. In my view, this piece of software is
truly first rate, and it has greatly improved my
productivity in the are
13 matches
Mail list logo
