Pierre GM wrote:
> All,
> Sorry to bumpt the post, accept my apologies for my rudeness, but I'm
> curious...
> So, let me rephrase my question:
>
> Many numpy functions (min, max, sum...) based on ndarray methods have a
> construction of the style
> #--
On Tuesday 24 June 2008 14:11:12 Robert Kern wrote:
> On Tue, Jun 24, 2008 at 13:03, Pierre GM <[EMAIL PROTECTED]> wrote:
> > Is this for efficiency purposes ?
>
> Most likely, the author just didn't realize that it might matter. Go
> ahead with your changes.
OK, great. Thanks a lot!
On Tue, Jun 24, 2008 at 13:03, Pierre GM <[EMAIL PROTECTED]> wrote:
> All,
> Sorry to bumpt the post, accept my apologies for my rudeness, but I'm
> curious...
> So, let me rephrase my question:
>
> Many numpy functions (min, max, sum...) based on ndarray methods have a
> construction of the style
All,
Sorry to bumpt the post, accept my apologies for my rudeness, but I'm
curious...
So, let me rephrase my question:
Many numpy functions (min, max, sum...) based on ndarray methods have a
construction of the style
#---
def amin(a, axis=None, out=Non
All,
is there a reason why in some functions (min, max...) optional parameters are
parsed by position instead of by keyword ?
OK, let me give you an example:
#---
def amin(a, axis=None, out=None):
try:
amin = a.min
except AttributeError:
