[Numpy-discussion] Release of 1.0b5 this weekend

Fernando Perez fperez.net at gmail.com
Tue Aug 29 16:25:08 CDT 2006

On 8/29/06, David M. Cooke <cookedm at physics.mcmaster.ca> wrote:
> On Tue, 29 Aug 2006 14:03:39 -0700
> Tim Hochberg <tim.hochberg at ieee.org> 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 case since we don't want to rewrite the sort routines)
> Ugh. That's completely different semantics from sort() on lists, so I think
> it would be a source of bugs (at least, it would mean keeping two different
> ideas of .sort() in my head).

Agreed.  Except where very well justified (such as slicing returning
views for memory reasons), let's keep numpy arrays similar to native
lists in their behavior...

Special cases aren't special enough to break the rules.

and all that :)



More information about the Numpy-discussion mailing list