Re: [Numpy-discussion] Assigning complex values to a real array

Anne Archibald wrote: > 2009/12/9 Dr. Phillip M. Feldman : > > >> When I recently tried to validate a code, the answers were wrong, and it >> took two full days to track down the cause. I am now forced to reconsider >> carefully whether Python/NumPy is a suitable platform for serious scientific

Re: [Numpy-discussion] Fixed-point arithemetic...any solution yet?

On Wed, Dec 9, 2009 at 8:26 PM, Neal Becker wrote: > Ruben Salvador wrote: > > > Hello everybody. > > > > I've seen this question arise sometimes on the list, but don't know if > > something has "happened" yet or not. I mean, any solution feasible to use > > more or less right out of the box? > >

Re: [Numpy-discussion] Assigning complex values to a real array

Thu, 10 Dec 2009 09:54:32 +0100, Dag Sverre Seljebotn wrote: [clip] > At this point I want to remind us about Charles Harris' very workable > proposal: Raise a warning. That should both keep backward compatability > and prevent people from wasting days. (Hopefully, we can avoid wasting > days discu

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 10:59:30AM +0100, Alexis Roche wrote: > Apparently you are trying to link nipy with an in-place build of > numpy, is that correct? Are you confident that the nipy setup does not > mix bits of your local numpy with another site-package install? My > question might be naive: I

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 05:29:07PM +0530, David Cournapeau wrote: > On Thu, Dec 10, 2009 at 5:13 PM, Gael Varoquaux > wrote: > > Does anybody have a suggestion on how to cleanly solve the problem? I > > fear I won't be the only one to have it. > The clean solution is to tell the deb package mai

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

to, 2009-12-10 kello 14:29 +0100, Gael Varoquaux kirjoitti: > On Thu, Dec 10, 2009 at 05:29:07PM +0530, David Cournapeau wrote: > > On Thu, Dec 10, 2009 at 5:13 PM, Gael Varoquaux > > wrote: > > > > > Does anybody have a suggestion on how to cleanly solve the problem? I > > > fear I won't be the

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 03:44:34PM +0200, Pauli Virtanen wrote: > Those who need alternative build chains can locate the path to the > correct numpy headers via > python -c 'import numpy, os; > print(os.path.dirname(numpy.__file__))+"/core/include"' > which is simple to pop in e.g. in a

Re: [Numpy-discussion] Fixed-point arithemetic...any solution yet?

On Thu, Dec 10, 2009 at 3:22 AM, Ruben Salvador wrote: > > On Wed, Dec 9, 2009 at 8:26 PM, Neal Becker wrote: > >> Ruben Salvador wrote: >> >> > Hello everybody. >> > >> > I've seen this question arise sometimes on the list, but don't know if >> > something has "happened" yet or not. I mean, any

Re: [Numpy-discussion] Numpy not reconising PA-RISC CPU on HP-UX workstation.

Charles R Harris wrote: > > > On Wed, Dec 9, 2009 at 12:13 PM, David Kirkby > wrote: > > See here for a fuller errror message, > > http://trac.sagemath.org/sage_trac/ticket/7166 > > but basically I see: > > gcc: build/src.hp-ux-B.11.11-9000-785

Re: [Numpy-discussion] Numpy not reconising PA-RISC CPU on HP-UX workstation.

On Thu, Dec 10, 2009 at 8:36 AM, Dr. David Kirkby wrote: > Charles R Harris wrote: > > > > > > On Wed, Dec 9, 2009 at 12:13 PM, David Kirkby > > wrote: > > > > See here for a fuller errror message, > > > > http://trac.sagemath.org/sage_trac/ticket/7166 > >

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 07:58, Gael Varoquaux wrote: > On Thu, Dec 10, 2009 at 03:44:34PM +0200, Pauli Virtanen wrote: >> Those who need alternative build chains can locate the path to the >> correct numpy headers via > >>         python -c 'import numpy, os; >> print(os.path.dirname(numpy.__file

Re: [Numpy-discussion] Assigning complex values to a real array

On Thu, Dec 10, 2009 at 04:24, Pauli Virtanen wrote: > Thu, 10 Dec 2009 09:54:32 +0100, Dag Sverre Seljebotn wrote: > [clip] >> At this point I want to remind us about Charles Harris' very workable >> proposal: Raise a warning. That should both keep backward compatability >> and prevent people fro

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 10:17:43AM -0600, Robert Kern wrote: > > OK, so we need to bug report to ubuntu. Anybody feels like doing it, or > > do I need to go ahead :). > It's your problem. :-) That's kinda what I thought. I was just try to dump work on someone else :). I'll do it. Gaël __

Re: [Numpy-discussion] Assigning complex values to a real array

On Thu, Dec 10, 2009 at 2:54 AM, Dag Sverre Seljebotn wrote: > Anne Archibald wrote: >> 2009/12/9 Dr. Phillip M. Feldman : >> >> >>> When I recently tried to validate a code, the answers were wrong, and it >>> took two full days to track down the cause.  I am now forced to reconsider >>> carefully

Re: [Numpy-discussion] Fixed-point arithemetic...any solution yet?

Dag Sverre Seljebotn wrote: > I haven't heard of anything, but here's what I'd do: > - Use np.int64 > - Multiply all inputs to my code with 10^6 > - Divide all output from my code with 10^6 > - If you need to debug-print and array, simply define something like > > FIXED_POINT_FACTOR = 10*

[Numpy-discussion] c++ code

Here is my c++ code if you want to play with it. You'll need to find constrained_value for boost (or I can provide it as a patch if you request). As for semantics, different people actually want/expect different behavior. I chose the 'pythonic' approach. If you do fpa @ fpb, where fpa,b are f

Re: [Numpy-discussion] Assigning complex values to a real array

to, 2009-12-10 kello 10:18 -0600, Robert Kern kirjoitti: > On Thu, Dec 10, 2009 at 04:24, Pauli Virtanen wrote: > > Thu, 10 Dec 2009 09:54:32 +0100, Dag Sverre Seljebotn wrote: > > [clip] > >> At this point I want to remind us about Charles Harris' very workable > >> proposal: Raise a warning. Tha

Re: [Numpy-discussion] Assigning complex values to a real array

Hi Pauli, On Thu, Dec 10, 2009 at 12:34 PM, Pauli Virtanen wrote: > to, 2009-12-10 kello 10:18 -0600, Robert Kern kirjoitti: > > On Thu, Dec 10, 2009 at 04:24, Pauli Virtanen > > > > wrote: > > > Thu, 10 Dec 2009 09:54:32 +0100, Dag Sverre Seljebotn wrote: > > > [clip] > > >> At this point I wa

[Numpy-discussion] Histogram - removing the "new" keyword for 1.4

Hi all, A long time ago, it was decided to change the default behaviour of the histogram function. The new behaviour has been the default in 1.3 and usage of the old behaviour has raised a warning. According to the timeline discussed at the time, version 1.4 would be the time to remove the old st

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 3:59 AM, David Cournapeau wrote: > You could also try playing with the order of the -Ipath to make sure > the right one us picked up before /usr/include, but I am not sure it > is even possible, as /usr/include may always be the first one gcc > looks in. Gael, orthogonal t

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 02:28:52PM -0800, Fernando Perez wrote: > and that's because for each one of these, I correctly configure ALL of these: > PATH: binary execution > LD_LIBRARY_PATH: dynamic linker search path > LIBRARY_PATH: static linking by gcc (like -L) > CPATH: generic include path for g

Re: [Numpy-discussion] [Nipy-devel] Impossibility to build nipy on recent numpy?

On Thu, Dec 10, 2009 at 2:40 PM, Gael Varoquaux wrote: > I have an aversion to changing LD_LIBRARY_PATH, LIBRARY_PATH, > C_INCLUDE_PATH, CPATH, and CPLUS_INCLUDE_PATH, because I believe it leads > to non reproducibles builds or run-time. > > More importantly, having to pull these tricks often reve

Re: [Numpy-discussion] Fixed-point arithemetic...any solution yet?

not to mention that that idea probably isnt going to work if his problem is non-linear ;) On Thu, Dec 10, 2009 at 7:36 PM, Norbert Nemec wrote: > > > Dag Sverre Seljebotn wrote: >> I haven't heard of anything, but here's what I'd do: >>   - Use np.int64 >>   - Multiply all inputs to my code with

Re: [Numpy-discussion] doctest improvements patch (and possible regressions)

On Wed, Dec 9, 2009 at 6:04 AM, Michael Droettboom wrote: > Sorry, just commenting on the parts I feel competent in :)  But I think > this is a great improvement.  It would be nice to start doing doctests > as a matter of course to keep the docs accurate. > Indeed. From the sidelines, thanks a l

[Numpy-discussion] Test reports of numpy 1.4.0.dev built with Visual Studio

Hello, I built Windows binaries of numpy-1.4.0rc2.dev7996 for Python 2.4, 2.5, and 2.6 (32 and 64-bit) using Microsoft Visual Studio 2003 and 2008. Looks good: the 'setup.py bdist_wininst' builds were all successful. The output of the 'python.exe -c "import numpy;numpy.test()"' runs are atta