Repository navigation
Conversation
… taken by Numpy's version of plot_directive. relative paths are now relative to the document.
…n check against it.
There was a problem hiding this comment.
This second entry in the CHANGELOG doesn't belong in this commit.
|
I tried building the docs on master with this patch. There are a few errors, many of which may not be directly related to these changes: I've seen ValueErrors like this before.: It probably means that at least one of the values in "segments" is bad, perhaps new plot_directive uncovered an existing problem in doc/examples/units/artist_tests.rst? This line in particular looks suspect (although I am not familiar enough with units support to know for sure): Here are a few additional errors I see when I build the docs: |
|
I believe most of these errors and warnings are resolved by this pull request: You may want to merge both to test. There are still some warnings we have been unable to get to the bottom of. See the comments in that pull request. |
|
In that case, would you consider merging my minor_doc_fixes branch into yours (just filed a pull request), closing this pull request (without merging into master) and then merging the plot_directive branch into the minor_doc_fixes branch? That way, it will be much easier to test and track down the remaining issues. |
…ot_directive Conflicts: lib/matplotlib/sphinxext/plot_directive.py
|
Ok. Your minor_doc_fixes branch and this plot_directive branch have been merged into minor_doc_fixes. |
moving directives to a relative path
This is a manually-intensive merge of the features Numpy's version of plot_directive that were missing from matplotlib's version. This allows the Numpy documentation to be build using matplotlib's plot_directive and addresses Numpy bug #1074:
http://projects.scipy.org/numpy/ticket/1074