One point which is often neglected while discussing oo- vs the pyplot-api is that today introspection tools quite often fail to work with mpl-oo but are perfectly fine with the pyplot module. E.g. if i am writing some kind of helper oder plotting function taking ax, one gets no auto-completion nor docstrings. I always have to use a interactive console to search for them or just type in the corresponding pyplot command for the function signature. Note that this is not matplotlibs fault, but another reason while beginners may prefer the pyplot-interface: Easier access to docstrings and available plotting functions.
This is also why i am a bit wary of using properties in matplotlib and i don't think they are a good fit most of the time. Documenting them is hard, discoverablity is also worse. And most setter methods in mpl have very useful kwargs, something which is not doable with properties. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
