Re: [Numpy-discussion] confusion about min/max

2007-09-18 Thread mark
Thanks guys. I personally like the amin, amax idea best. But that is just me, Mark > > or, as you said, import max explicitly. > > Or use numpy.amin and numpy.amax, which are included in numpy.__all__, > just as you use numpy.arange in place of range. > > Eric > ___

[Numpy-discussion] ANN: Trilinos 8.0, including PyTrilinos 4.0

2007-09-18 Thread Bill Spotz
Version 8.0 of Trilinos has been released: http://trilinos.sandia.gov Trilinos is a collection of scientific, object-oriented solver packages. These packages cover linear algebra services, preconditioners, linear solvers, nonlinear solvers, eigensolvers, and a wide range of related ut

Re: [Numpy-discussion] confusion about min/max

2007-09-18 Thread Eric Firing
stefan wrote: > On Tue, 18 Sep 2007 13:07:29 +0200, Gael Varoquaux > <[EMAIL PROTECTED]> wrote: >> On Tue, Sep 18, 2007 at 10:33:29AM -, mark wrote: >>> Does that make sense? I know, I should probably use a.min() rather >>> than min(a), but why does min() not get imported on an import * ? >> Be

Re: [Numpy-discussion] Anyone have a well-tested SWIG-based C++ STL valarray <=> numpy.array typemap to share?

2007-09-18 Thread Charles R Harris
On 9/17/07, David Cournapeau <[EMAIL PROTECTED]> wrote: > > Christopher Barker wrote: > > David Cournapeau wrote: > >> Christopher Barker wrote: > >>> My real question is what compiler and library writers are doing -- has > >>> anyone (OK, I guess MS and gcc are all I care about anyway) built > >>>

Re: [Numpy-discussion] Anyone have a well-tested SWIG-based C++ STL valarray <=> numpy.array typemap to share?

2007-09-18 Thread Matthieu Brucher
> > My understanding of blitz is that it is supposed to be faster mainly > because it can avoid temporaries thanks to expression template. In fact, Boost.uBLAS uses expression templates as well. Matthieu ___ Numpy-discussion mailing list Numpy-discussi

[Numpy-discussion] FPE on tensordot

2007-09-18 Thread Alexandre Fayolle
Hi, A user of some code I've written is experiencing some strange behaviour with numpy.tensordot. I have unfortunately no access to his computer and cannot reproduce the crash on my machine. The short way of reproducing this is: import numpy a=numpy.array([0.5,0.5]) b=numpy.array([[0.,1.],[2.,3.

Re: [Numpy-discussion] confusion about min/max

2007-09-18 Thread stefan
On Tue, 18 Sep 2007 13:07:29 +0200, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > On Tue, Sep 18, 2007 at 10:33:29AM -, mark wrote: >> Does that make sense? I know, I should probably use a.min() rather >> than min(a), but why does min() not get imported on an import * ? > > Because min isn't in

Re: [Numpy-discussion] confusion about min/max

2007-09-18 Thread Gael Varoquaux
On Tue, Sep 18, 2007 at 10:33:29AM -, mark wrote: > Does that make sense? I know, I should probably use a.min() rather > than min(a), but why does min() not get imported on an import * ? Because min isn't in numpy.__all__. Python imports only identifiers listed in __all__ if __all__ is present

[Numpy-discussion] confusion about min/max

2007-09-18 Thread mark
Hello - When I am doing from numpy import * It does not import the min() function, but when I do from numpy import min it does import the min() function Does that make sense? I know, I should probably use a.min() rather than min(a), but why does min() not get imported on an import * ? Thank