On 2011-03-07 08:59, Benjamin Root wrote:
> On Mon, Mar 7, 2011 at 10:33 AM, Yuri D'Elia<[email protected]> wrote:
>> I was reading this at the time:
>>
>> http://matplotlib.sourceforge.net/faq/usage_faq.html
>>
>> I inferred pyplot was just a matlab-like interface on top of matplotlib,
>> and figured using directly the matplotlib was acceptable.
>>
>
> Yeah, I am guessing that page is a little out-dated and could be better
> worded. However, the page does say that the preferred style is the pyplot
> interface. Also notice that it is extremely rare for any of the
> documentation to directly create the matplotlib objects without the pyplot
> or pylab interface.
I think this documentation should definitely be updated, then. I've
been using matplotlib a lot the last few months and was totally
unaware that pyplot was "required". Good thing I read this message! :-)
> The interface should create the figure objects, the figure objects should
> create the axes objects, the axes objects should create the axis objects,
> and so on and so forth.
That makes perfect sense, but is not at all what's implied by the
text on the page linked above.
Best wishes,
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is
no path, and leave a trail."
--author unknown
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Matplotlib-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
