On Thu, 9 Dec 2010 12:57:49 -0600, John Hunter <jdh2...@gmail.com> wrote: > 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.
It seems that this may have been broken from the beginning. After noticing that my changes were not taking effect, I added some debug output and found that sphinx was changing the current working directory (every example gets built with its own directory being the working directory). I fail to see how doc/matplotlibrc could be currently used given most examples are not built from doc/. > and these are picked up at build time since the rest table formatting > of the API docs depends on the latter setting. > Are you certain this configuration isn't leaking in from some other source? > And yes, the relative paths in sphinx doc builds are a major headache. Are you referring to the fact that sphinx's above-mentioned chdir behavior? Cheers, - Ben ------------------------------------------------------------------------------ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
