On Sat, Jul 21, 2007 at 11:34:07AM -0400, Paul Kienzle wrote:
Feel free to tune the list appropriately. Particularly since max/min/abs
already do the right things with vectors:
Hell, not with anything that more than 1D ! Beware.
Gaël
John Hunter wrote:
[...]
functions or array functions here, eg math.sqrt vs numpy.sqrt? Also,
a few of your symbols clash with python builtins (min, max, abs) which
is best avoided. Finally, how would you feel about allowing these
symbols in the module namespace, but w/o the import *
On 7/21/07, Paul Kienzle [EMAIL PROTECTED] wrote:
True
min(a)
1
min(b)
We should prefer the numpyisms anyway, a.max(), a.min(), a.absolute().
Finally, how would you feel about allowing these
symbols in the module namespace, but w/o the import * semantics, eg,
for these symbols
John Hunter wrote:
We should prefer the numpyisms anyway, a.max(), a.min(), a.absolute().
Exactly -- OO semantics make the whole namespace thing much more workable.
To sum up a bit -- This all started with a comment about how some of the
pylab names clash with numpy names, so that:
from pylab
On Sat, Jul 21, 2007 at 08:51:19AM -1000, Eric Firing wrote:
John Hunter wrote:
[...]
functions or array functions here, eg math.sqrt vs numpy.sqrt? Also,
a few of your symbols clash with python builtins (min, max, abs) which
is best avoided. Finally, how would you feel about allowing
