Re: [Numpy-discussion] numpy.all docstring reality check

2010-07-01 Thread Benjamin Root
This behavior is quite curious. While it is consistent and it behaves exactly as documented (after clarification), I am curious about the rational. Is it merely an unavoidable consequence of passing in the output array? Certainly a few examples from the above emails would make this extremely cle

Re: [Numpy-discussion] numpy.all docstring reality check

2010-06-29 Thread David Goldsmith
OK, now I understand: dtype(out) is preserved, whatever that happens to be, not dtype(a) (which is what I thought it meant) - I better clarify. Thanks! DG On Tue, Jun 29, 2010 at 7:28 PM, Skipper Seabold wrote: > On Tue, Jun 29, 2010 at 8:50 PM, David Goldsmith > wrote: > > Hi, folks. Under P

Re: [Numpy-discussion] numpy.all docstring reality check

2010-06-29 Thread Skipper Seabold
On Tue, Jun 29, 2010 at 8:50 PM, David Goldsmith wrote: > Hi, folks.  Under Parameters, the docstring for numpy.core.fromnumeric.all > says: > > "out : ndarray, optionalAlternative output array in which to place the > result. It must have the same shape as the expected output and the type is > pre

[Numpy-discussion] numpy.all docstring reality check

2010-06-29 Thread David Goldsmith
Hi, folks. Under Parameters, the docstring for numpy.core.fromnumeric.all says: "out : ndarray, optionalAlternative output array in which to place the result. It must have the same shape as the expected output and *the type is preserved*." [emphasis added].I assume this is a copy-and-paste-from-a