Re: [Numpy-discussion] Proposal for a new function: np.moveaxis

I'm just a lowly user, but I'm a fan of this. +1! On Thu, Nov 5, 2015 at 6:42 PM, Stephan Hoyer wrote: > I've put up a pull request implementing a new function, np.moveaxis, as an > alternative to np.transpose and np.rollaxis: > https://github.com/numpy/numpy/pull/6630 > This functionality has b

Re: [Numpy-discussion] querying backend information

On Thu, Nov 5, 2015 at 1:37 AM, Ralf Gommers wrote: > > > On Thu, Nov 5, 2015 at 5:11 AM, Nathaniel Smith wrote: > >> On Wed, Nov 4, 2015 at 4:40 PM, Stefan Seefeld >> wrote: >> > Hello, >> > >> > is there a way to query Numpy for information about backends (BLAS, >> > LAPACK, etc.) that it was

Re: [Numpy-discussion] Proposal for a new function: np.moveaxis

Also a +1 from me. I've had to (re-)learn how exactly np.transpose works more times then I care to admit. - Jonathan Helmus On 11/05/2015 02:26 AM, Juan Nunez-Iglesias wrote: > I'm just a lowly user, but I'm a fan of this. +1! > > > > > On Thu, Nov 5, 2015 at 6:42 PM, Stephan Hoyer

[Numpy-discussion] Compilation problems npy_float64

Hello, I searched the forum, but couldn't find a post related to my problem. I am installing scipy via pip in cygwin environment pip install scipy Note: numpy version 1.10.1 was installed with pip install -U numpy /usr/bin/gfortran -Wall -g -Wall -g -shared -Wl,-gc-sections -Wl,-s build

Re: [Numpy-discussion] Compilation problems npy_float64

Thu, 05 Nov 2015 16:26:18 +, Johan kirjoitti: > Hello, I searched the forum, but couldn't find a post related to my > problem. I am installing scipy via pip in cygwin environment [clip] > /usr/include/math.h:263:15: note: previous declaration ‘double > infinity()’ > extern double infi

Re: [Numpy-discussion] New behavior of allclose

On Wed, Nov 4, 2015 at 8:28 PM, Charles R Harris wrote: > Hi All, > > This is to open a discussion of a change of behavior of `np.allclose`. > That function uses `isclose` in numpy 1.10 with the result that array > subtypes are preserved whereas before they were not. In particular, memmaps > are

Re: [Numpy-discussion] New behavior of allclose

allclose() needs to return a bool so that one can do "if np.allclose(foo, bar) is True" or some such. The "good behavior" is for np.isclose() to return a memmap, which still confuses the heck out of me, but I am not a memmap expert. On Thu, Nov 5, 2015 at 4:50 PM, Ralf Gommers wrote: > > > On We

Re: [Numpy-discussion] New behavior of allclose

On Thu, Nov 5, 2015 at 2:50 PM, Ralf Gommers wrote: > > > On Wed, Nov 4, 2015 at 8:28 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> This is to open a discussion of a change of behavior of `np.allclose`. >> That function uses `isclose` in numpy 1.10 with the result