On Thu, Dec 9, 2010 at 12:34 PM, Ben Gamari <bgam...@gmail.com> wrote:
> Regardless, after making the necessary changes to use absolute paths > (after painfully realizing that the MATPLOTLIB environment variable > expects the directory of the desired matplotlibrc, not the file path; > documentation would have been nice here) the configuration is _still_ > having no effect. While matplotlib.matplotlib_fname() seems to be > reporting the correct matplotlibrc path, examples.download is still True > despite setting this to False in the file. Sorry to be joining this a bit late. Why do you need to set the MATPLOTLIBRC variable. The file doc/matplotlibrc is used by the doc build process, so if you patch in your changes there, you should be good. Specifically, we set the parameters backend : Agg docstring.hardcopy : True and these are picked up at build time since the rest table formatting of the API docs depends on the latter setting. And yes, the relative paths in sphinx doc builds are a major headache. Sorry you are having so much trouble. We struggled mightily against them in trying to get the plot directive working. In my experience, setting relative paths with respect to the doc root (where conf.py lives) works in most cases. ------------------------------------------------------------------------------ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
