Closed gagern closed 7 years ago
I should have done a better job. I was on the sphinx bug so I knew it would hit the tree and potentially affect you people on ~arch. You have sphinx-1.5.1
don't you?
1.5.1-r1, yes.
I'll have to look into the changes needed for 1.5.x
in the meantime I will pin the sphinx dependency a bit better.
Ok, sage should now pull sphinx-1.4.4
and the problem shouldn't happen.
I'm in the process of downgrading sphinx and building sage with that, but it will take a while to complete. Will close this issue once that succeeds. Thanks for the quick reaction!
I had a look at the file, and can't see why sphinx would consider tuple
a reference there. I don't see any special markup to make it that. The line most likely to trigger this would be
:type X: integer or list, tuple, or other iterable
but on the one hand that looks like plain text, not links, and on the other hand even if the words were to denote types, they should refer to classes or built-in types, not methods. Strange, but feels like a bug in sphinx.
Do you have any idea of how to invoke sphinx in order to reproduce the kind of invocation Sage does? If so, it might be worth bisecting this in the sphinx repo.
Not directly. The recipe I have in the ebuild is the best thing I have:
"${PYTHON}" sage_setup/docbuild/__main__.py --no-pdf-links all html
OK, I got past the error I originally reported, but now I encounter a different error. Probably unrelated, though, so I'll close this one here.
Yes, after fixing #451 the build succeeded, so the sphinx version was indeed the problem.
Sage fails to build its documentation for me.
Is this an upstream issue, or something at the ebuild level?