Re: [Numpy-discussion] flatnonzero fails with lists

On Mon, Feb 24, 2014 at 10:37 PM, Alan G Isaac wrote: > I was surprised that `flatnonzero` fails with lists > because it calls the `ravel` method, which they do not have, > instead of using the `ravel` function. > > I do not know that there is any policy that NumPy > functions should always work

[Numpy-discussion] flatnonzero fails with lists

I was surprised that `flatnonzero` fails with lists because it calls the `ravel` method, which they do not have, instead of using the `ravel` function. I do not know that there is any policy that NumPy functions should always work on lists, but I have gotten used to them doing so. So I'm just aski

Re: [Numpy-discussion] 1.8.1 release

When will we see a http://sourceforge.net/projects/numpy/files/NumPy/1.8.1/Changelog/download changelog? I'd like to get this into our organization's SRS, and a list of fixes (related or not) would be great. - Ray ___ NumPy-Discussion mailing list NumP

Re: [Numpy-discussion] 1.8.1 release

What's up with the OpenBLAS work? Any chance that might make it into official binaries? Or is is just too fresh? Also -- from an off-hand comment in the thread is looked like OpenBLAS could provide a library that selects for optimized code at run-time depending on hardware -- this would solve the

Re: [Numpy-discussion] recfunctions

On February 25, 2014 at 01:26:51 , Charles R Harris (charlesr.har...@gmail.com) wrote: Hi All, Does anyone recall if it was a deliberate choice to not expose recfunctions in the lib package? This is apropos issue #4242. Yes. This job was a rip-off of John Hunter’s similar functions on matplo

[Numpy-discussion] recfunctions

Hi All, Does anyone recall if it was a deliberate choice to not expose recfunctions in the lib package? This is apropos issue #4242 . Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://m

Re: [Numpy-discussion] 1.8.1 release

Hi, On Mon, Feb 24, 2014 at 12:40 PM, Matthew Brett wrote: > Hi, > > On Sun, Feb 23, 2014 at 10:26 AM, Charles R Harris > wrote: >> Hi All, >> >> A lot of fixes have gone into the 1.8.x branch and it looks about time to do >> a bugfix release. There are a couple of important bugfixes still to >>

Re: [Numpy-discussion] 1.8.1 release

I am pretty sure that you guys test pandas master but 1.8.1 looks good to me > On Feb 24, 2014, at 4:42 PM, Charles R Harris > wrote: > > > > >> On Mon, Feb 24, 2014 at 1:54 PM, RayS wrote: >> Has anyone alerted C Gohlke? >> http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy >> >> - Ray >

Re: [Numpy-discussion] 1.8.1 release

On Mon, Feb 24, 2014 at 1:54 PM, RayS wrote: > Has anyone alerted C Gohlke? > http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy > > - Ray > Christolph seems to keep a pretty good eye on numpy and we rely on him to test it on windows. In anycase, there are enough fixes backported, that I think we

Re: [Numpy-discussion] 1.8.1 release

Has anyone alerted C Gohlke? http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy - Ray ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] 1.8.1 release

Hi, On Sun, Feb 23, 2014 at 10:26 AM, Charles R Harris wrote: > Hi All, > > A lot of fixes have gone into the 1.8.x branch and it looks about time to do > a bugfix release. There are a couple of important bugfixes still to > backport, but if all goes well next weekend, March 1, looks like a good

Re: [Numpy-discussion] argsort speed

On Fri, Feb 21, 2014 at 11:09 PM, Charles R Harris wrote: > > > > On Fri, Feb 21, 2014 at 10:35 PM, Ondřej Čertík > wrote: >> >> On Mon, Feb 17, 2014 at 11:40 AM, Charles R Harris >> wrote: >> > >> > >> > >> > On Mon, Feb 17, 2014 at 11:32 AM, Julian Taylor >> > wrote: >> >> >> >> On 17.02.2014

[Numpy-discussion] problems building numpy with ACML blas/lapack

Hello, I'm trying to build numpy from source to use AMD's ACML for matrix multiplication (specifically the multi-threaded versions gfortran64_mp). I'm able to successfully compile and use a working version of np.dot, but my resulting installation doesn't pass numpy's test suite, instead, I get a s

Re: [Numpy-discussion] Proposal: Chaining np.dot with mdot helper function

Hey guys, I just pushed an updated version to github: https://github.com/sotte/numpy_mdot Here is an ipython notebook with some experiments: http://nbviewer.ipython.org/urls/raw2.github.com/sotte/numpy_mdot/master/2014-02_numpy_mdot.ipynb - I added (almost numpy compliant) documentation. - I use

Re: [Numpy-discussion] How exactly ought 'dot' to work?

>> 23.02.2014 00:03, Nathaniel Smith kirjoitti: >>> Currently numpy's 'dot' acts a bit weird for ndim>2 or ndim<1. In >>> practice this doesn't usually matter much, because these are very >>> rarely used. But, I would like to nail down the behaviour so we can >>> say something precise in the matrix

Re: [Numpy-discussion] np.savetxt() default format

On 24 February 2014 13:26, Daniele Nicolodi wrote: > Hello, > > I've noticed that numpy default format for saving data in ascii > representation with np.savetxt() is "%.18e". Given that the default > data type for numpy is double and that the resolution of doubles is 15 > decimal digits, what's t

[Numpy-discussion] np.savetxt() default format

Hello, I've noticed that numpy default format for saving data in ascii representation with np.savetxt() is "%.18e". Given that the default data type for numpy is double and that the resolution of doubles is 15 decimal digits, what's the reason of the the additional three digits? The three additi

Re: [Numpy-discussion] How exactly ought 'dot' to work?

On 24 February 2014 05:21, Nathaniel Smith wrote: > > I've tentatively rewritten the first section of the PEP to try and > accomplish this framing: > > https://github.com/njsmith/numpy/blob/matmul-pep/doc/neps/return-of-revenge-of-matmul-pep.rst > Comments welcome etc. I've not been following