Well, if I can cast a vote, it would make a lot of sense if pylab functions
do the same thing as numpy functions. Right now it is exceedingly confusing
when I teach, that zeros() could be integers or floats. An rc parameter
where we would import straight from numpy would be most excellent. Can't
w
Gary Ruben wrote:
> Hi Mark,
> this thread may help:
> http://thread.gmane.org/gmane.comp.python.numeric.general/13399/focus=13421
>
> Essentially, pylab uses a compatibility layer to ease the task of
> supporting the three array packages - currently this uses the Numeric
> version of the ones a
Hi Mark,
this thread may help:
http://thread.gmane.org/gmane.comp.python.numeric.general/13399/focus=13421
Essentially, pylab uses a compatibility layer to ease the task of
supporting the three array packages - currently this uses the Numeric
version of the ones and zeros functions giving the be
"Mark Bakker" <[EMAIL PROTECTED]> writes:
> Can this be fixed? Any explanation how this happens? Pylab just
> imports part of numpy, doesn't it?
It imports numerix, a compatibility layer for numeric, numarray and
numpy. I think the plan is to remove numerix soon and just use numpy,
but in the mea
Hello list -
I am confused about the part of numpy that pylab imports.
Apparently, pylab imports 'zeros', but not the 'zeros' from numpy, as it
returns integers by default, rather than floats.
The same holds for 'ones' and 'empty'.
Example:
from pylab import *
zeros(3)
array([0, 0, 0])
from nu
