Alan McIntyre gmail.com> writes:
>
> On Mon, Nov 16, 2009 at 11:34 PM, "V. Armando Solé" esrf.fr> wrote:
> > Sebastian Berg wrote:
> >> Known issue, I think someone posted about it a while ago too. The numpy
> >> min is array aware, and it expects an array. The second argument is the
> >> axis,
On Mon, Nov 16, 2009 at 11:34 PM, "V. Armando Solé" wrote:
> Sebastian Berg wrote:
>> Known issue, I think someone posted about it a while ago too. The numpy
>> min is array aware, and it expects an array. The second argument is the
>> axis, which in the case of a single number doesn't matter.
>
>
Sebastian Berg wrote:
> Known issue, I think someone posted about it a while ago too. The numpy
> min is array aware, and it expects an array. The second argument is the
> axis, which in the case of a single number doesn't matter.
>
> On Tue, 2009-11-17 at 07:07 +, Chris wrote:
>
>> I'm pret
On Mon, Nov 16, 2009 at 11:07 PM, Chris wrote:
> I'm pretty sure this shouldn't happen:
>
> In [1]: from numpy import min
>
> In [2]: min(5000, 4)
> Out[2]: 5000
The way you're calling it is working like this: min((5000,) , axis=4)
so you'd need to do this instead: min((5000,4))
_
Known issue, I think someone posted about it a while ago too. The numpy
min is array aware, and it expects an array. The second argument is the
axis, which in the case of a single number doesn't matter.
On Tue, 2009-11-17 at 07:07 +, Chris wrote:
> I'm pretty sure this shouldn't happen:
>
> I
I'm pretty sure this shouldn't happen:
In [1]: from numpy import min
In [2]: min(5000, 4)
Out[2]: 5000
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
