Re: [matplotlib-devel] Reorganizing axes plot methods

[Eric F. <ef...@ha...>]

On 2013/07/17 3:14 AM, Michael Droettboom wrote:
> Yes.  This is great work!
>
> Just to chime in (after having been away for most of this conversation) -->
>
> I think we can do this reorganization now without introducing any
> implicit (or otherwise) use of gca()/pyplot stuff in the Axes class
> methods.  Refactoring how the pyplot wrapper is done can be done as a
> separate project at a later time (or even in parallel if someone wants
> to, since all of Nelle's work at the end of the day doesn't change the
> Axes interface).
>
> My only other comment (and I mentioned this in PR #2213 as well) is that
> having the short stub functions in the Axes class in addition to the
> actual implementations elsewhere introduces a new
> synchronization/maintenance problem between the two.  Maybe it makes
> sense to merely add the implementation functions to the Axes class
> namespace dynamically.  Magical, sure, but should have ultimately the
> same result as far as introspection, autocompletion and other IPython
> goodness is concerned.
>
> Mike

Mike,

One other option is to have the new private modules include mixin 
classes from which Axes would inherit methods.  There would be a lot of 
mixins, and this would be an example of the dreaded multiple 
inheritance, but it would be simple and explicit, with no magic.

Eric