Re: [Numpy-discussion] Binary releases

2013-09-23 Thread Charles R Harris
On Mon, Sep 23, 2013 at 6:22 PM, David Cournapeau wrote: > Ok, so I've looked a bit into it tonight: > > - used mingw-w64 4.8.1 (32 bits host) > - openblas binaries available on the official website (seem to be built > with mingw w64) > - used -static-libgcc, -static-libstdc++ and -static-libgf

Re: [Numpy-discussion] Binary releases

2013-09-23 Thread josef . pktd
On Mon, Sep 23, 2013 at 8:22 PM, David Cournapeau wrote: > Ok, so I've looked a bit into it tonight: > > - used mingw-w64 4.8.1 (32 bits host) > - openblas binaries available on the official website (seem to be built > with mingw w64) > - used -static-libgcc, -static-libstdc++ and -static-libgf

Re: [Numpy-discussion] Binary releases

2013-09-23 Thread David Cournapeau
Ok, so I've looked a bit into it tonight: - used mingw-w64 4.8.1 (32 bits host) - openblas binaries available on the official website (seem to be built with mingw w64) - used -static-libgcc, -static-libstdc++ and -static-libgfortran - building numpy went ok, test suite almost passes, nothing t

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Charles R Harris
On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris wrote: > > > > On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock wrote: > >> On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris >> wrote: >> > Hi All, >> > >> > I have gotten no feedback on the removal of the numarray and oldnumeric >> > packages. Conse

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Charles R Harris
On Mon, Sep 23, 2013 at 3:18 PM, Charles R Harris wrote: > > > > On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock wrote: > >> On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris >> wrote: >> > Hi All, >> > >> > I have gotten no feedback on the removal of the numarray and oldnumeric >> > packages. Conse

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Charles R Harris
On Mon, Sep 23, 2013 at 2:42 PM, Peter Cock wrote: > On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris > wrote: > > Hi All, > > > > I have gotten no feedback on the removal of the numarray and oldnumeric > > packages. Consequently the removal will take place on 9/28. Scream now or > > never... >

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Peter Cock
On Mon, Sep 23, 2013 at 6:03 PM, Charles R Harris wrote: > Hi All, > > I have gotten no feedback on the removal of the numarray and oldnumeric > packages. Consequently the removal will take place on 9/28. Scream now or > never... > > Chuck Hi Chuck, Could you clarify how we'd know if this is a p

Re: [Numpy-discussion] Pull request review #3770: Trapezoidal distribution

2013-09-23 Thread Jeremy Hetzel
On Sun, Sep 22, 2013 at 9:47 AM, Mark Szepieniec wrote: > > On Sun, Sep 22, 2013 at 1:24 PM, wrote: > >> >> I don't see a reason that numpy.random shouldn't get new >> distributions. It would also be useful to add the corresponding >> distribution to scipy.stats. >> > I have the pdf, cdf, and i

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Perry Greenfield
We at STScI have no objection. If we have any residual dependencies, we'll then find out and fix them. Perry On Sep 23, 2013, at 1:03 PM, Charles R Harris wrote: > Hi All, > > I have gotten no feedback on the removal of the numarray and oldnumeric > packages. Consequently the removal will tak

[Numpy-discussion] Generating a (uniformly distributed) random bit list of length N

2013-09-23 Thread David Goldsmith
speed or memory use? The operation you show should > already be quite fast. A more memory efficient approach would be to > generate integers and use their binary representation. > > St?fan > -- next part -- > An HTML attachment was scrubbed... > URL: > h

[Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Charles R Harris
Hi All, I have gotten no feedback on the removal of the numarray and oldnumeric packages. Consequently the removal will take place on 9/28. Scream now or never... Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/m

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Derek Homeier
On 23.09.2013, at 7:03PM, Charles R Harris wrote: > I have gotten no feedback on the removal of the numarray and oldnumeric > packages. Consequently the removal will take place on 9/28. Scream now or > never... The only thing I'd care about is the nd_image subpackage, but as far as I can see,

Re: [Numpy-discussion] Removal of numarray and oldnumeric packages.

2013-09-23 Thread Charles R Harris
On Mon, Sep 23, 2013 at 11:21 AM, Derek Homeier < de...@astro.physik.uni-goettingen.de> wrote: > On 23.09.2013, at 7:03PM, Charles R Harris > wrote: > > > I have gotten no feedback on the removal of the numarray and oldnumeric > packages. Consequently the removal will take place on 9/28. Scream n

Re: [Numpy-discussion] openblas?

2013-09-23 Thread Dag Sverre Seljebotn
On 09/23/2013 02:27 PM, Neal Becker wrote: > Does numpy/scipy support building with openblas for blas,lapack instead of > atlas? I have that working myself. I think it was simply a matter of using the configuration below; NumPy will think it is ATLAS, but that doesn't matter. Once NumPy is built

[Numpy-discussion] openblas?

2013-09-23 Thread Neal Becker
Does numpy/scipy support building with openblas for blas,lapack instead of atlas? ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Runtime Warning by numpy.divide(0.0, 0.0) can't be ignored

2013-09-23 Thread Robert Kern
On Monday, September 23, 2013, Lorenzo Di Gregorio wrote: > Hello, > > numpy.divide(0.0,0.0) raises a warning which doesn't appear to get caught > by numpy.seterr(divide='ignore') > > This example: > > import numpy > numpy.divide(0.0,0.0) > numpy.divide(1.0,0.0) > numpy.seterr(divide='ignore') > n

[Numpy-discussion] Runtime Warning by numpy.divide(0.0, 0.0) can't be ignored

2013-09-23 Thread Lorenzo Di Gregorio
Hello, numpy.divide(0.0,0.0) raises a warning which doesn't appear to get caught by numpy.seterr(divide='ignore') This example: import numpy numpy.divide(0.0,0.0) numpy.divide(1.0,0.0) numpy.seterr(divide='ignore') numpy.divide(1.0,0.0) numpy.divide(0.0,0.0) produces this output: Warning (from