On Dec 11, 2007 5:42 PM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > On Tue, Dec 11, 2007 at 05:37:41PM -0700, Fernando Perez wrote: > > The tconfig objects already have a very dict-like representation for > > dumping into a text file, the .ini format. Or do you mean something > > that's even closer to a dict, curly braces and all? > > No, I don't care about the curly brace. However, I don't want the > comments. I haven't decided yet, but I am sure that I want something that > a bit more compact than, eg "print MPLConfig()".
I see, makes sense. Hack away, I trust your judgment :) > > > The problem is that it would break your script, so I can't send you a > > > patch. I'd like the codebase to stay similar, so maybe we can discuss > > > this once I have some code. > > > Yup, it would be good not to have mpl-tconfig, ipython-tconfig and > > mayavi-tconfig :) > > Yes, lets try to keep this united. I'll probably also work on a nice > TraitsUI view. If all three projects can use the same model, view and > controler for the configuration file, that will make it easier to, one > day, present a unified configuration editor for a scientific IDE (:->). Indeed. Once we have the code in place, we'll worry about organizing things for easy reuse. Cheers, f ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
