On Monday 12 November 2007 06:39:28 pm Darren Dale wrote: > On Monday 12 November 2007 05:52:55 pm John Hunter wrote: > > On Nov 12, 2007 4:09 PM, Darren Dale <[EMAIL PROTECTED]> wrote: > > > I have been updating the logic in our setup.py and setupext.py files, > > > so all of the build options are now exposed in setup.cfg. This should > > > make it easier for anyone wishing to distribute matplotlib, like > > > package managers. See setup.cfg.template for the details. > > > > I just did a clean build and it went through -- a good start! I tried > > enabling the new config with by setting NEWCONFIG = True in > > __init__.py, and also enabled in setup.cfg
I altered mplconfig to create a matplotlib.conf.template file, which gets read and modified at build time like we do with matplotlibrc.template. It's not as elegant as using the config package machinery to create the default config file at build time, but I think this will serve our needs. Devs still need to execute mplconfig.py when we make changes that would affect the default config file. I also updated the selection of the default backend at build time: SVG -> Agg -> TkAgg -> WXAgg -> GTK -> GTKAagg -> selection in setup.cfg committed in svn-4242. Darren ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
