Re: [matplotlib-devel] [Fwd: Re: [Distutils] Confusion about the effect of eggs on import]

[Tim L. <tim...@gm...>]

On 2/11/07, John Hunter <jd...@gm...> wrote:
> On 2/10/07, Tim Leslie <tim...@gm...> wrote:
>
> > And for what it's worth this is also the direction nipy is taking,
> > having an api.py in each package.
>
> I don't have a problem with this if it makes sense to other people and
> helps with consistency across packages, but I don't find the mnemonic
> particularly clear.  Eg
>
>   from matplotlib.config import rc, verbose
>
> makes more sense to me than
>
>   from matplotlib.api import rc, verbose
>
> since I consider these (and most other stuff in  __init__) to be part
> of the configuration, and a lot of stuff that doesn't live there
> (Figure, Axes, Line2D) to be part of the API.  What is the
> enthought/nipy rationale for calling it api?
>

Sorry, I think I might have given the wrong impression. Our use of an
api.py is for having a single location to import classes equivalent to
Figure, Axes, etc from. Your suggestion of having a matplotlib.config
for things like rc and verbose makes a lot of sense I think.

Tim

> JDH
>