Actually, since it's the package that most users probably actually want,
would it be more suitable to move matplotlib.matlab into matplotlib
itself? Then we could simply
Obviously that would mix the main user routines (plot()...) with the
more administrative namespace (get_backend(), is_interactive()...) and
maybe you'd want to move those into a separate (always imported)
subpackage along the lines of matplotlib.res?
Just an idea.
>From: John Hunter <jdhunter@...>
>Date: Mon, 29 Nov 2004 17:23:04 -0600
>Subject: [Matplotlib-users] matlab (TM)
>I'm concerned that at some point down the road, The Mathworks may not
>like the fact that matplotlib uses the name matlab, which is
>trademarked. I think I'll rename the matlab interface to pylab. In
>some sense, this name is more appropriate any way, because I'd like to
>incorporate the best features of IDL, gnuplot and python, while still
>retaining and enhancing core matlab compatibility. I emailed Travis,
>who previously used pylab.sf.net before it became part of scipy, and
>he didn't have a problem with our using this name. And Fernando
>already uses pylab as the option to ipython to make ipython support
>So my plan is to change the name of the matplotlib.matlab module to
>matplotlib.pylab, but wanted propose this here first since this will
>effect almost every script. It should be an easy search and replace
>operation, and I'll probably post a little python script to
>recursively replace all matplotlib.matlab references in a given
>directory with matplotlib.pylab, since I have a few directories myself
>that will need to be renamed.
>Comments or objections welcome.
This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.