On Fri, Jul 20, 2007 at 03:25:06PM -0600, Fernando Perez wrote: > 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. That really depends whether you what mplconfig to be able to provide its own abstract layer over tconfig, with possibly modified ConfigManager and mkConfigObj (remember EZvisage). I don't think it is the case here, but I kust wanted to point out that I am not sure this is allways good coding practice. My 2 euro cents, Gaël ------------------------------------------------------------------------- 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
