Eric Firing wrote:
> I do not think mlab
> should "from numpy import *"; if that is what someone wants, they can do
> it explicitly themselves, very easily. Now, pylab should do something
> like "from mlab import *; from numpy import *; from pyplot import *",
> but mlab should be its own nice,
Christopher Barker wrote:
> Ryan May wrote:
>>> I for one will be happy to change my code; numerical stuff in
>>> numpy, plotting stuff in pylab (or pyplot?), though some things
>>> like linspace() may be hard to loose; that's really an mlab
>>> function and I can import mlab.
>
> I'm a big namesp
Ryan May wrote:
>> I for one will be happy to change my code; numerical stuff in
>> numpy, plotting stuff in pylab (or pyplot?), though some things
>> like linspace() may be hard to loose; that's really an mlab
>> function and I can import mlab.
I'm a big namespace fan. I'd much rather see us all
Tom Holroyd (NIH/NIMH) [E] wrote:
[...]
>
> For the C library you say "man strcpy" or "man erf" and it tells you
> what include file to use to get the definition (function prototype). In
> python you only get the help after you've already imported. But it was
> and still is reasonable to have a
Just a bad example. I know there are functions that were originally defined in
Matlab and then got rewritten in python, but I've never been clear on which
modules they really live in.
Ryan May wrote:
> Tom Holroyd (NIH/NIMH) [E] wrote:
>> Eric Firing wrote:
>>> Similarly, after dealing with mla
Tom Holroyd (NIH/NIMH) [E] wrote:
>
> Eric Firing wrote:
>> Similarly, after dealing with mlab, I would like to simplify pylab.
>> Right now, we have a horrible tangle of namespaces in pylab. Cleaning
>> this up will potentially break user code; if a numpy function formerly
>> could be referen
Eric Firing wrote:
> Similarly, after dealing with mlab, I would like to simplify pylab.
> Right now, we have a horrible tangle of namespaces in pylab. Cleaning
> this up will potentially break user code; if a numpy function formerly
> could be referenced with three different names and we kno
Hi Eric,
thanks for the warning. I had looked into the issue but never got around
to start working on it.
While you are at it, I would suggest that you split the graphics stuff
out of pylab into a separate
module (pyplot?) to be used for "interactive plotting".
I believe I'm not the only user wh
Mike,
It is a good question.
Right now I am doing some of each. If a function was defined in mlab.py
and it has a replacement in numpy I am issuing a deprecation warning
and passing the arguments to the numpy function. If a function was not
defined in mlab but was imported from numerix, the
Eric Firing wrote:
> Similarly, after dealing with mlab, I would like to simplify pylab.
> Right now, we have a horrible tangle of namespaces in pylab. Cleaning
> this up will potentially break user code; if a numpy function formerly
> could be referenced with three different names and we knock
I have been gradually numpifying mlab.py; I hope this is not a
duplication of effort with someone else. I have not finished yet (and
have made no commits), and it may still take a while--there are a lot of
things to change, and I am trying to do some cleaning up and
rationalization, not just me
11 matches
Mail list logo
