On Tuesday 15 May 2007 17:34:15 Charles R Harris wrote:
> I see no one answered ;) I think it is traditional behaviour from Numeric,
> so can't be changed without a bit of thought.
> Why not file a ticket for the
> 1.1 release and see how folks respond?
I'll try to.
> Is there any reason why
On 5/8/07, Pierre GM <[EMAIL PROTECTED]> wrote:
All,
On a 2D array, numpy.core.umath.maximum.reduce returns a 1D array (the
default axis is 0). An axis=None is not recognized as a valid argument
for
numpy.core.umath.maximum, unfortunately... Is this the wanted behavior ?
Thanks a lot in advance
All,
On a 2D array, numpy.core.umath.maximum.reduce returns a 1D array (the
default axis is 0). An axis=None is not recognized as a valid argument for
numpy.core.umath.maximum, unfortunately... Is this the wanted behavior ?
Thanks a lot in advance
P.
_
