Eric Firing wrote: > Tom Holroyd (NIH/NIMH) [E] wrote: >> >> Ted Drain wrote: >>> I think the basic idea is that if I want to use MPL, I should import >>> it and go and I should not have to import a sub-module out of MPL as >>> the main API. >> >> Yeah, about that, my typical usage is actually "from pylab import *". >> I guess I am unclear about the relationship between matplotlib and pylab. >> > > Tom, > > matplotlib is the object-oriented plotting library; pylab is a module > within matplotlib that provides a matlab-style (state-machine) interface > to the library. > > Eric
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? -- Tom Holroyd, Ph.D. "The fundamentally misconceived nature versus nurture debate should be abandoned: child development is inextricably both." -- Louann Brizendine ------------------------------------------------------------------------- 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
