Re: [Numpy-discussion] Release of 1.0b5 this weekend

On Tuesday 29 August 2006 19:24, Fernando Perez wrote: > On 8/29/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Classes start for me next Tuesday, and I'm teaching a class for which I > > will be using NumPy / SciPy extensively. I need to have a release of > > these two (and ho

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > > Hi all, > > Classes start for me next Tuesday, and I'm teaching a class for which I > will be using NumPy / SciPy extensively. I need to have a release of > these two (and hopefully matplotlib) that work with each other. > > Therefore, I'm

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, Charles R Harris <[EMAIL PROTECTED]> wrote: On 8/29/06, Tim Hochberg <[EMAIL PROTECTED] > wrote: David M. Cooke wrote:> On Tue, 29 Aug 2006 14:03:39 -0700> Tim Hochberg <[EMAIL PROTECTED] > wrote: Of these,  clip, conjugate and round support an 'out' argument like that >> supported

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, Tim Hochberg <[EMAIL PROTECTED]> wrote: David M. Cooke wrote:> On Tue, 29 Aug 2006 14:03:39 -0700> Tim Hochberg <[EMAIL PROTECTED]> wrote: Of these,  clip, conjugate and round support an 'out' argument like that >> supported by ufunces;  byteswap has a boolean argument telling it>>

Re: [Numpy-discussion] Release of 1.0b5 this weekend

David M. Cooke wrote: > On Tue, 29 Aug 2006 14:03:39 -0700 > Tim Hochberg <[EMAIL PROTECTED]> wrote: > > >> Of these, clip, conjugate and round support an 'out' argument like that >> supported by ufunces; byteswap has a boolean argument telling it >> whether to perform operations in place; a

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On Tue, 29 Aug 2006, Tim Hochberg apparently wrote: > b = a.sort() # Returns a copy Given the extant Python vocabulary, this seems like a bad idea to me. (Better to call it 'sorted' in this case.) fwiw, Alan Isaac - Usi

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Hi,On 8/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:>I find it much cleaner to write>x = foo.bar().baz(param).frob() >than>foo.bar()>foo.baz(param)>x = foo.frob()>but perhaps others disagree.Both of these look "clean" but i do not think that moving 3 lines to oneline makes code "cleaner"  T

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, David M. Cooke <[EMAIL PROTECTED]> wrote: > On Tue, 29 Aug 2006 14:03:39 -0700 > Tim Hochberg <[EMAIL PROTECTED]> wrote: > > b = a.sort() # Returns a copy > > a.sort(out=a) # Sorts a in place > > a.sort(out=c) # Sorts a into c (probably just equivalent to c = a.sort() > > in this cas

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On Tue, 29 Aug 2006 13:25:14 -0600 "Charles R Harris" <[EMAIL PROTECTED]> wrote: > Hi Fernando, > > On 8/29/06, Fernando Perez <[EMAIL PROTECTED]> wrote: > > > > On 8/29/06, Charles R Harris <[EMAIL PROTECTED]> wrote: > > > > > Speaking of features, I wonder if more of the methods should return >

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Hi Tim,On 8/29/06, Tim Hochberg <[EMAIL PROTECTED]> wrote: Charles R Harris wrote:>>> On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED]> [EMAIL PROTECTED] >> wrote:>> Charles R Harris wrote:> > Hi,> >> > On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> > [EMAIL

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On Tue, 29 Aug 2006 14:03:39 -0700 Tim Hochberg <[EMAIL PROTECTED]> wrote: > Of these, clip, conjugate and round support an 'out' argument like that > supported by ufunces; byteswap has a boolean argument telling it > whether to perform operations in place; and sort always operates in > place

Re: [Numpy-discussion] Release of 1.0b5 this weekend

>I find it much cleaner to write >x = foo.bar().baz(param).frob() >than >foo.bar() >foo.baz(param) >x = foo.frob() >but perhaps others disagree. Both of these look "clean" but i do not think that moving 3 lines to one line makes code "cleaner" They both do the same thing and if someone that d

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Charles R Harris wrote: > > > On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED] > > wrote: > > Charles R Harris wrote: > > Hi, > > > > On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED] > > >

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Fernando Perez wrote: > more 'return self' at the end of methods which currently don't > return anything (well, we get the default None), as long as it's > sensible. +1 Though I'm a bit hesitant: if it's really consistent that methods that alter the object in place NEVER return themselves, the

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Tim Hochberg wrote: >-0.5 from me if what we're talking about here is having mutating methods >return self rather than None. Chaining stuff is pretty, but having >methods that mutate self and return self looks like a source of elusive >bugs to me. > > I'm generally +0 on this idea (it seems

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Charles R Harris wrote: > > The 1.0rc1 release of NumPy will be mid September I suspect. > > Also, I recognize that the default-axis switch is a burden for > those who > have already transitioned code to use NumPy (for those just > starting out > it's not a big deal because

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, Tim Hochberg <[EMAIL PROTECTED]> wrote: Charles R Harris wrote:> Hi,>> On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED]> [EMAIL PROTECTED] >> wrote:>>> -0.5 from me if what we're talking about here is having mutating> methods> return self rather than None. Chaining stuff is pre

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Charles R Harris wrote: > Hi, > > On 8/29/06, *Tim Hochberg* <[EMAIL PROTECTED] > > wrote: > > > -0.5 from me if what we're talking about here is having mutating > methods > return self rather than None. Chaining stuff is pretty, but having > methods that

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On Tue, 29 Aug 2006, Tim Hochberg apparently wrote: > -0.5 from me if what we're talking about here is having > mutating methods return self rather than None. Chaining > stuff is pretty, but having methods that mutate self and > return self looks like a source of elusive bugs to me. I believe

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Hi,On 8/29/06, Tim Hochberg <[EMAIL PROTECTED]> wrote: -0.5 from me if what we're talking about here is having mutating methodsreturn self rather than None. Chaining stuff is pretty, but havingmethods that mutate self and return self looks like a source of elusive bugs to me.-timBut how is that any

Re: [Numpy-discussion] Release of 1.0b5 this weekend

-0.5 from me if what we're talking about here is having mutating methods return self rather than None. Chaining stuff is pretty, but having methods that mutate self and return self looks like a source of elusive bugs to me. -tim Rudolph van der Merwe wrote: > This definitely gets my vote as

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Hi Fernando,On 8/29/06, Fernando Perez <[EMAIL PROTECTED]> wrote: On 8/29/06, Charles R Harris <[EMAIL PROTECTED]> wrote:> Speaking of features, I wonder if more of the methods should return> references. For instance, it might be nice to write something like: >>  a.sort().searchsorted([...])>> inst

Re: [Numpy-discussion] Release of 1.0b5 this weekend

This definitely gets my vote as well (for what it's worth). R. On 8/29/06, Fernando Perez <[EMAIL PROTECTED]> wrote: > +1 for more 'return self' at the end of methods which currently don't > return anything (well, we get the default None), as long as it's > sensible. I really like this 'message

Re: [Numpy-discussion] Release of 1.0b5 this weekend

On 8/29/06, Charles R Harris <[EMAIL PROTECTED]> wrote: > Speaking of features, I wonder if more of the methods should return > references. For instance, it might be nice to write something like: > > a.sort().searchsorted([...]) > > instead of making two statements out of it. +1 for more 'return

Re: [Numpy-discussion] Release of 1.0b5 this weekend

Hi Travis,On 8/29/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: Hi all,Classes start for me next Tuesday, and I'm teaching a class for which Iwill be using NumPy / SciPy extensively.  I need to have a release ofthese two (and hopefully matplotlib) that work with each other. Therefore, I'm going to

[Numpy-discussion] Release of 1.0b5 this weekend

Hi all, Classes start for me next Tuesday, and I'm teaching a class for which I will be using NumPy / SciPy extensively. I need to have a release of these two (and hopefully matplotlib) that work with each other. Therefore, I'm going to make a 1.0b5 release of NumPy over the weekend (probabl