On 7/20/07, Darren Dale <[EMAIL PROTECTED]> wrote: > On Friday 20 July 2007 05:25:06 pm Fernando Perez wrote: > > I also just (r2528) updated things to use a cleaner import convention: > > I don't like importing things from modules *they* imported. > [...] > > The point is that instead of > > > > -from mplconfig import MPLConfig, ConfigManager, mkConfigObj > > > > I prefer: > > > > +from tconfig import ConfigManager, mkConfigObj > > +from mplconfig import MPLConfig > > > > since ConfigManager and mkConfigObj really live in tconfig, I'm not > > tying my top-level code to an implementation detail of an intermediate > > module (what it imports and how it names it). I mention this > > explicitly just because I think it's a good bit of coding practice. > > I was thinking along the lines of your config/api.py file, a single entry > point to the ipython or mpl config API.
Ah, OK. Since we haven't really organized such an api yet, I was still thinking of the individual components. I see your point. Cheers, f ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
