Tom Holroyd (NIH/NIMH) [E] wrote: [...] > If I say > >>>> import matplotlib >>>> help(matplotlib) > > (This is with 0.90.0 by the way) > > It basically gives me the help I'd expect for pylab. Oh, and it says > "the" instead of "to". It's a little weird thinking of a library as the > top level with the main interface as a module. I guess the interface is > just another component of the library. Though when I > >>>> import pylab >>>> help(pylab) > > I get what looks like help for numpy. Perhaps my installation is strange? >
I have fixed this. The problem was that when you import pylab, it imports a stub "pylab.py" from site-packages, which in turn imports everything from matplotlib/pylab.py. The matplotlib.pylab docstring does not get transferred to the newly loaded pylab module, however. The solution was to do that transfer explicitly in the pylab.py stub. I also made slight tweaks to the pylab.py and matplotlib.py docstrings to try to clarify the pylab-matplotlib relationship. The matplotlib docstring still blathers on about pylab functions, however; I suspect we should change this to something more unique and helpful, such as a directory of matplotlib submodules and/or an intro to the useful things in matplotlib.__init__.py like rcParams. Eric ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
