Re: [Numpy-discussion] failure

2009-01-23 Thread Jarrod Millman
On Wed, Jan 21, 2009 at 10:53 AM, Gideon Simpson wrote: > == > FAIL: test_umath.TestComplexFunctions.test_against_cmath > -- > Traceback (most recent call last):

Re: [Numpy-discussion] Pattern for reading non-simple binary files

2009-01-23 Thread Eric Firing
Ryan May wrote: > Hi, > > I'm trying to read in a data from a binary-formatted file. I have the data > format, (available at: > http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td7000.pdf if you're > really curious), but it's not what I would consider simple, with a lot of > different bloc

Re: [Numpy-discussion] Pattern for reading non-simple binary files

2009-01-23 Thread Robert Kern
On Fri, Jan 23, 2009 at 15:31, Ryan May wrote: > Hi, > > I'm trying to read in a data from a binary-formatted file. I have the data > format, (available at: > http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td7000.pdf if you're > really curious), but it's not what I would consider simple,

[Numpy-discussion] Pattern for reading non-simple binary files

2009-01-23 Thread Ryan May
Hi, I'm trying to read in a data from a binary-formatted file. I have the data format, (available at: http://www1.ncdc.noaa.gov/pub/data/documentlibrary/tddoc/td7000.pdf if you're really curious), but it's not what I would consider simple, with a lot of different blocks and messages, some that are

Re: [Numpy-discussion] coding style: citations

2009-01-23 Thread Alan G Isaac
Tim Michelsen wrote: > did you already come to a conclusion regarding this cite topic? > Did you try to run the bibtext extension for Sphinx? > If so, please update the documentation guidelines. I hope we reached agreement that the documentation should use reST citations and not reST footnotes. Y

Re: [Numpy-discussion] strange multiplication behavior with numpy.float64 and ndarray subclass

2009-01-23 Thread Darren Dale
On Wed, Jan 21, 2009 at 1:07 PM, Darren Dale wrote: > > > On Wed, Jan 21, 2009 at 12:26 PM, Pierre GM wrote: > >> > I dont understand why __array_priority__ is not being respected >> > here. Ticket 826 lists the component as numpy.ma, it seems the >> > problem is in numpy.core. I think the sever

[Numpy-discussion] ANN: Numexpr 1.1.1 available

2009-01-23 Thread Francesc Alted
== Announcing Numexpr 1.1.1 == Numexpr is a fast numerical expression evaluator for NumPy. With it, expressions that operate on arrays (like "3*a+4*b") are accelerated and use less memory than doing the same calculation in Python. This is a bug-fi

Re: [Numpy-discussion] coding style: citations

2009-01-23 Thread Stéfan van der Walt
Hi Tim 2009/1/22 Tim Michelsen : > did you already come to a conclusion regarding this cite topic? > > Did you try to run the bibtext extension for Sphinx? I haven't tried it. One difficulty is that each docstring needs to be self-contained, i.e., it must include its own references. If you want

Re: [Numpy-discussion] coding style: citations

2009-01-23 Thread Tim Michelsen
Hello Allan, Stefan and others, did you already come to a conclusion regarding this cite topic? Did you try to run the bibtext extension for Sphinx? If so, please update the documentation guidelines. Regards, Timmie ___ Numpy-discussion mailing list N

Re: [Numpy-discussion] python numpy code many times slower than c++

2009-01-23 Thread Robert Kern
On Thu, Jan 22, 2009 at 17:09, Wes McKinney wrote: > Windows XP, Pentium D, Python 2.5.2 I can replicate the negative numbers on my Windows VM. I'll take a look at it. Wrote profile results to foo.py.lprof Timer unit: 4.17601e-010 s File: foo.py Function: f at line 1 Total time: -3.02963 s Lin

Re: [Numpy-discussion] Numpy unexpected (for me) behaviour

2009-01-23 Thread Robert Kern
On Fri, Jan 23, 2009 at 02:10, V. Armando Sole wrote: > At 01:44 23/01/2009 -0600, Robert Kern wrote: >>It is an inevitable consequence of several features interacting >>together. Basically, Python expands "a[b] += 1" into this: >> >> c = a[b] >> d = c.__iadd__(1) >> a[b] = d >> >>Basically,

Re: [Numpy-discussion] Numpy unexpected (for me) behaviour

2009-01-23 Thread V. Armando Sole
At 01:44 23/01/2009 -0600, Robert Kern wrote: >It is an inevitable consequence of several features interacting >together. Basically, Python expands "a[b] += 1" into this: > > c = a[b] > d = c.__iadd__(1) > a[b] = d > >Basically, the array c doesn't know that it was created by indexing a, >so