matplotlib-devel Mailing List for matplotlib

On Sun, Dec 5, 2010 at 3:14 PM, Ben Gamari <bga...@gm...> wrote:
>> I am not intimately familiar with the doc build system, but the way that
>> the "html" function in make.py copies matplotlibrc from mpl-data to
>> _static, I suspect that it is trying to ensure that that particular file
>> is used.
>>
> Anyone else have further guidance?
No, that is there so that the link from the customizing page
 http://matplotlib.sourceforge.net/users/customizing.html
to the "download matplotlibrc" link
 http://matplotlib.sourceforge.net/_static/matplotlibrc
works and gives an update matplotlibrc. It is not used in the doc
build to customize the settings of the docs. The files in _static are
just copied up to the web server but can be linked to from withing
rest.
JDH

On 2010年12月05日 23:03:02 +0200, Jouni K. Seppänen <jk...@ik...> wrote:
> Ben Gamari <bga...@gm...>
> writes:
> 
> > In practice, however, I have run into a few issues. First, the comment
> > regarding examples.directory indicates that this path must be
> > absolute. Is this really true? 
> 
> The comment is wrong: a relative path will work (I just tried this).
> 
Awesome. Perhaps this should be corrected in the tree so it doesn't look
like I'm blatantly violating the documentation?
> > Secondly, it seems that the doc/matplotlibrc file is completely
> > ignored.
> 
> I am not intimately familiar with the doc build system, but the way that
> the "html" function in make.py copies matplotlibrc from mpl-data to
> _static, I suspect that it is trying to ensure that that particular file
> is used.
>
Anyone else have further guidance?
- Ben

On 2010年12月05日 23:03:02 +0200, Jouni K. Seppänen <jk...@ik...> wrote:
> Ben Gamari <bga...@gm...>
> writes:
> 
> > In practice, however, I have run into a few issues. First, the comment
> > regarding examples.directory indicates that this path must be
> > absolute. Is this really true? 
> 
> The comment is wrong: a relative path will work (I just tried this).
> 
Awesome. Perhaps this should be corrected in the tree so it doesn't look
like I'm blatantly violating the documentation?
> > Secondly, it seems that the doc/matplotlibrc file is completely
> > ignored.
> 
> I am not intimately familiar with the doc build system, but the way that
> the "html" function in make.py copies matplotlibrc from mpl-data to
> _static, I suspect that it is trying to ensure that that particular file
> is used.
>
Anyone else have further guidance?
- Ben

Ben Gamari <bga...@gm...>
writes:
> In practice, however, I have run into a few issues. First, the comment
> regarding examples.directory indicates that this path must be
> absolute. Is this really true? 
The comment is wrong: a relative path will work (I just tried this).
> Secondly, it seems that the doc/matplotlibrc file is completely
> ignored.
I am not intimately familiar with the doc build system, but the way that
the "html" function in make.py copies matplotlibrc from mpl-data to
_static, I suspect that it is trying to ensure that that particular file
is used.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On Mon, 8 Nov 2010 14:01:26 -0600, John Hunter <jd...@gm...> wrote:
> I will try and get to the release ASAP and set the sample_data up this way...
> 
Any news on this? A release would be very nice. I did the bulk of the
work[1] to get the debian packaging working with the 1.0 series but I
can't really do much else until there is an actual release to work
against.
- Ben
[1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial
 Although this isn't quite working yet. More about this in another
 thread.

This weekend I put a bit of time into bringing the Debian packaging[1]
for the matplotlib 1.0 series up to date.
In the tree it seems there is a matplotlibrc in the /doc
directory. Judging from the documentation, it looks like matplotlib will
first use a matplotlibrc in the current directory. This works very well
for the case of packaging for Debian, since I can simply override the
examples.* options here to avoid downloading the samples while building
the documentation.
In practice, however, I have run into a few issues. First, the comment
regarding examples.directory indicates that this path must be
absolute. Is this really true? For obvious reasons we don't know the
absolute path of the samples until we actually build the package. I
suppose an 'echo' in the packaging makefile could dynamically patch this
path in, but a relative path would be far simpler.
Secondly, it seems that the doc/matplotlibrc file is completely ignored.
When I tried building with "examples.directory=../sampledata", I still
saw multiple failed download attempts in the package build log. Indeed,
even putting an invalid line in doc/matplotlibrc doesn't result in an
error.
For the record, the documentation build process is invoked with,
 cd doc ; MATPLOTLIBDATA=../lib/matplotlib/mpl-data/ \
 PYTHONPATH=../build/lib.$(PY_PLATFORM)-$(DEFPY) ./make.py --small all
Any suggestions would be greatly appreciated.
- Ben
[1] https://launchpad.net/~bgamari/+archive/matplotlib-unofficial