On Fri, Oct 25, 2013 at 3:32 PM, Todd <toddr...@gmail.com> wrote:
> I think one thing that contributes a lot to the API issues is the
> inconsistency between pyplot API and the OO API. There isn't any reason
> the APIs need to be so different.
>
indeed.
I hadn't even realized how different they were.
> So the idea would be to have essentially all of the pyplot functions just
> be wrappers for methods from other classes, using the same name and same
> call signature (minus "self"). All of the actual functionality would be
> implemented in the methods, the pyplot functions should not have any logic
> or tests.
>
+ inf
However, doing this with full backward compatibility could be a real
challenge...
This will make it easy to transition between the two, learning to use the
> OO interface would just involve learning what object the pyplot function is
> targeting (this should be in the pyplot function docstring).
>
That would help, though a namespace without any non-OO stuff would be still
be good, and, of course, docs and tutorials.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
chris.bar...@noaa.gov
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
