Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Sat, Mar 5, 2011 at 11:11 AM, Charles R Harris wrote: > On Fri, Mar 4, 2011 at 7:49 PM, Charles R Harris > wrote: >> On Fri, Mar 4, 2011 at 6:41 PM, Charles R Harris >> wrote: >>> On Fri, Mar 4, 2011 at 12:54 PM, Christoph Gohlke >>> wrote: Most packages don't have any apparent problems

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 4, 2011 at 9:11 PM, Charles R Harris wrote: > > > On Fri, Mar 4, 2011 at 7:49 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Fri, Mar 4, 2011 at 6:41 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> >>> >>> On Fri, Mar 4, 2011 at 12:54 PM, Ch

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Sat, Mar 5, 2011 at 3:54 AM, Christoph Gohlke wrote: > > > On 3/4/2011 1:00 AM, Christoph Gohlke wrote: > > I tested the 32 and 64 bit msvc9/MKL builds for Python 2.7 and 3.2. > There are few test failures (listed below) that look familiar. > > I also ran tests and/or examples of a few 3rd part

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 4, 2011 at 5:00 PM, Christoph Gohlke wrote: > > > On 3/3/2011 10:54 PM, Ralf Gommers wrote: >> Before the first beta can be released I think #1748 should be fixed. >> Before the first RC the Solaris segfaults should be investigated, and >> documentation for the new iterator (Python doc

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 4, 2011 at 7:49 PM, Charles R Harris wrote: > > > On Fri, Mar 4, 2011 at 6:41 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Fri, Mar 4, 2011 at 12:54 PM, Christoph Gohlke wrote: >> >>> >>> >>> On 3/4/2011 1:00 AM, Christoph Gohlke wrote: >>> > >>> > >>> > On

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 4, 2011 at 6:41 PM, Charles R Harris wrote: > > > On Fri, Mar 4, 2011 at 12:54 PM, Christoph Gohlke wrote: > >> >> >> On 3/4/2011 1:00 AM, Christoph Gohlke wrote: >> > >> > >> > On 3/3/2011 10:54 PM, Ralf Gommers wrote: >> >> On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers >> >> wrote

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 4, 2011 at 12:54 PM, Christoph Gohlke wrote: > > > On 3/4/2011 1:00 AM, Christoph Gohlke wrote: > > > > > > On 3/3/2011 10:54 PM, Ralf Gommers wrote: > >> On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers > >> wrote: > >>> On Mon, Feb 28, 2011 at 10:36 PM, Bruce Southey > >>> wrote: > >

[Numpy-discussion] Request for a bit more info on structured arrays in the "basics" page

The page gives a good introduction to structured arrays. However, it says nothing about how to set a particular element (all fields at once) from a collection of data. For instance: stArr = numpy.zeros([4,5], dtype=[("pos", float, (2,)), (

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

Thanks (again) for taking this on Ralf. You are doing a superb job and deserve much thanks for keeping the NumPy project on track. I'm very encouraged by the NumPy 1.6 work. I was looking over the code some more on the plane yesterday that Mark Wiebe has checked in (I finally was able to cr

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On Fri, Mar 04, 2011 at 11:54:07AM -0800, Christoph Gohlke wrote: > I also ran tests and/or examples of a few 3rd party packages that were > built against numpy 1.5.1: scipy, pygame, PyMOL, numexpr, matplotlib, > basemap, scikits.learn, ETS.mayavi, Bottleneck, pytables, and pandas. Wow, this is

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On 3/4/2011 11:54 AM, Christoph Gohlke wrote: > > > On 3/4/2011 1:00 AM, Christoph Gohlke wrote: >> >> >> On 3/3/2011 10:54 PM, Ralf Gommers wrote: >>> On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers >>> wrote: On Mon, Feb 28, 2011 at 10:36 PM, Bruce Southey wrote: > On 02/28/2011

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On 3/4/2011 1:00 AM, Christoph Gohlke wrote: > > > On 3/3/2011 10:54 PM, Ralf Gommers wrote: >> On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers >> wrote: >>> On Mon, Feb 28, 2011 at 10:36 PM, Bruce Southey >>> wrote: On 02/28/2011 02:00 AM, Ralf Gommers wrote: > Hi, > > On Fri, J

Re: [Numpy-discussion] generic slicing question

Den 04.03.2011 15:19, skrev Neal Becker: > This will subtract col 0 from all cols of a 2-d array: > > # subtract col 0 from all cols > def ll2llr (m): > return m - m[:,0][:,np.newaxis] > > > In general, how to subtract the (n-1)d slice at index 0 from all elements of > an > n-d array? > > (I

Re: [Numpy-discussion] Taking a large number of dot products at once

Den 04.03.2011 14:55, skrev Sturla Molden: or just to write more Pythonic code. We don't need to write FORTRAN in Python, computers are fast. Don't be afraid of Python containers and for-loops. They are not nearly as evil as Matlab's for loops used to be. Also operations like appending tend

[Numpy-discussion] generic slicing question

This will subtract col 0 from all cols of a 2-d array: # subtract col 0 from all cols def ll2llr (m): return m - m[:,0][:,np.newaxis] In general, how to subtract the (n-1)d slice at index 0 from all elements of an n-d array? (I think a 3d version is: m - m[:,:,0][:,:,np.newaxis] ) ___

Re: [Numpy-discussion] Taking a large number of dot products at once

Den 04.03.2011 14:55, skrev Sturla Molden: We can do this with Python lists of NumPy arrays as well, avoiding stacking the arrays in a 2D structure: [np.dot(u,v.T) for u,v in zip(U,V)] Damn it, bad style. Inner product, not outer... [np.dot(u.T,v) for u,v in zip(U,V)] or just [

Re: [Numpy-discussion] Taking a large number of dot products at once

Den 04.03.2011 07:19, skrev Daniel Hyams: This is probably so easy, I'm embarrassed to ask it...but I've been casting around trying things to no avail for the last hour and a half, so here goes... I have a lot of dot products to take. The length-3 vectors that I want to dot are stacked in a

Re: [Numpy-discussion] Taking a large number of dot products at once

On Fri, Mar 4, 2011 at 4:13 AM, Hector wrote: > > > On Fri, Mar 4, 2011 at 12:59 PM, eat wrote: >> >> Hi, >> >> On Fri, Mar 4, 2011 at 8:19 AM, Daniel Hyams wrote: >>> >>> This is probably so easy, I'm embarrassed to ask it...but I've been >>> casting around trying things to no avail for the las

Re: [Numpy-discussion] Taking a large number of dot products at once

On Fri, Mar 4, 2011 at 12:59 PM, eat wrote: > Hi, > > On Fri, Mar 4, 2011 at 8:19 AM, Daniel Hyams wrote: > >> This is probably so easy, I'm embarrassed to ask it...but I've been >> casting around trying things to no avail for the last hour and a half, so >> here goes... >> >> I have a lot of do

Re: [Numpy-discussion] Numpy 1.6 schedule (was: Numpy 2.0 schedule)

On 3/3/2011 10:54 PM, Ralf Gommers wrote: On Mon, Feb 28, 2011 at 11:31 PM, Ralf Gommers wrote: On Mon, Feb 28, 2011 at 10:36 PM, Bruce Southey wrote: On 02/28/2011 02:00 AM, Ralf Gommers wrote: Hi, On Fri, Jan 28, 2011 at 7:15 AM, Travis Oliphant wrote: The reason for a NumPy 1.6 s