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 mlab, I
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 just finished writing code to support scalable mathtext with the Cairo
backend. (The old version rendered the mathtext to bitmaps first).
Mostly straightforward, but I ran into one small snag. It *seems* that
pycairo requires that the fonts it uses are installed and accessible
through
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 do
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, clean
