Re: [Numpy-discussion] Warning: invalid value encountered in divide

2011-08-08 Thread Wes McKinney
On Mon, Aug 8, 2011 at 7:01 PM, Neal Becker wrote: > Warning: invalid value encountered in divide > > No traceback.  How can I get more info on this?  Can this warning be converted > to an exception so I can get a trace? > > ___ > NumPy-Discussion mailin

[Numpy-discussion] Warning: invalid value encountered in divide

2011-08-08 Thread Neal Becker
Warning: invalid value encountered in divide No traceback. How can I get more info on this? Can this warning be converted to an exception so I can get a trace? ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman

Re: [Numpy-discussion] Weird upcast behavior with 1.6.x, working as intended?

2011-08-08 Thread Olivier Delalleau
2011/8/8 Charles R Harris > > > On Mon, Aug 8, 2011 at 10:54 AM, Olivier Delalleau wrote: > >> Hi, >> >> This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism >> of "scalar + array": >> >> >>> import numpy; print (numpy.array(3, dtype=numpy.complex128) + >> numpy.ones(3, dtyp

Re: [Numpy-discussion] Weird upcast behavior with 1.6.x, working as intended?

2011-08-08 Thread Charles R Harris
On Mon, Aug 8, 2011 at 10:54 AM, Olivier Delalleau wrote: > Hi, > > This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism > of "scalar + array": > > >>> import numpy; print (numpy.array(3, dtype=numpy.complex128) + > numpy.ones(3, dtype=numpy.float32)).dtype > complex64 > > Si

[Numpy-discussion] Weird upcast behavior with 1.6.x, working as intended?

2011-08-08 Thread Olivier Delalleau
Hi, This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism of "scalar + array": >>> import numpy; print (numpy.array(3, dtype=numpy.complex128) + numpy.ones(3, dtype=numpy.float32)).dtype complex64 Since it has to upcast my array (float32 is not "compatible enough" with comple

Re: [Numpy-discussion] [ANN] Cython 0.15

2011-08-08 Thread Christopher Barker
On 8/8/11 1:21 AM, Sebastian Haase wrote: > b) What is the status of supporting multi-type Cython functions -- ala > C++ templates ? You might want to take a look at what Keith Goodman has done with the "Bottleneck" project -- I think he used a generic template tool to generate Cython code for

Re: [Numpy-discussion] [ANN] Cython 0.15

2011-08-08 Thread Sturla Molden
Den 08.08.2011 11:47, skrev Dag Sverre Seljebotn: > This come up now and again and I believe there's several > half-baked/started solutions out there by Cython users, but nothing > that is standard or that I know is carried out to completion. I.e., > you should ask on the cython-users list. It'd

[Numpy-discussion] PEP 3118 array size check

2011-08-08 Thread Angus McMorland
Hi all, I've just upgraded to the latest numpy from git along with upgrading Ubuntu to natty. Now some of my code, which relies on ctypes-wrapping of data structures from a messaging system, fails with the error message: "RuntimeWarning: Item size computed from the PEP 3118 buffer format string d

Re: [Numpy-discussion] [ANN] Cython 0.15

2011-08-08 Thread Dag Sverre Seljebotn
On 08/08/2011 10:21 AM, Sebastian Haase wrote: > On Sun, Aug 7, 2011 at 11:24 PM, Dag Sverre Seljebotn > wrote: >> On 08/07/2011 10:31 PM, Paul Anton Letnes wrote: >>> Looks like you have done some great work! I've been using f2py in the past, >>> but I always liked the idea of cython - graduall

Re: [Numpy-discussion] [ANN] Cython 0.15

2011-08-08 Thread Sebastian Haase
On Sun, Aug 7, 2011 at 11:24 PM, Dag Sverre Seljebotn wrote: > On 08/07/2011 10:31 PM, Paul Anton Letnes wrote: >> Looks like you have done some great work! I've been using f2py in the past, >> but I always liked the idea of cython - gradually wrapping more and more >> code as the need arises. I