Repository navigation
DOC: fix references in docs - #13104
Conversation
|
Hey can I work on this? |
|
Anyone is welcome to work on this. You should read up on building the documentation and then
|
can you get rid of that somehow @mattip? |
|
We should merge this as-is, it improves the current situation. I opened #13114 with the content of the first comment for more work. |
|
Merged, thanks @mattip |
|
for the record, TravisCI did complete, it just failed to report its status back to this PR |
I've observed that in a few places when using the official Draft Status mode for PRs. |
I followed the steps written, but I got error in conf.py I guess I know what the error is about. On line 132 in conf.py with this helps. |
|
The error here is supposed to guide you how to solve the problem: try running |
Turning on
-ninsphinx-buildresults in over 1000 warnings about bad references in docs. Trying to break these down with various grep statements, it seems about 200 are fromnumpy.ma, about 150 frompolynomialand about 150 fromc:type. That is under half of the WARNINGS.My workflow is to run
and look for the most common lines. Unfortunately this takes quite a while.
Anyone who wishes to contribute can issue PRs against the
doc-referencesbranch in numpy/mattip. I have marked this as Easy since many of the WARNINGS are quite easy to fix. The first commit gives an idea of some of the problems in the c-api documentation.Reviewers can get an idea of how bad things are by looking at the circle-ci devdoc build step.