[Numpy-discussion] isn't it a bug in array.fill()?
Charles R Harris
Fri Aug 29 16:18:35 CDT 2008
On Fri, Aug 29, 2008 at 3:03 PM, Alan G Isaac <firstname.lastname@example.org> wrote:
> Stéfan van der Walt wrote:
> > At first, I also thought it might be more intuitive to return the
> > output array, but then I realised that it would make it more difficult
> > to realise that the operation is being performed in-place. Maybe it
> > is good to remind programmers of what happens under the hood, so that
> > they are not surprised later when their data is "corrupted".
> That is essentially the core reason for the behavior of list.sort().
IIRC, it is also the case that Guido doesn't like the a.foo().bar().oops()
style of programming, preferring one operation/line.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Numpy-discussion