-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC: Use sphinxcontrib-apidoc and various cleanups #1010
Conversation
How does it relate to #570? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome stuff thanks @effigies! Clearly you're way ahead on the Sphinx workings than I am and I really appreciate your time to improve this ahead of the 5.0.0 release (this weekend!).
I'm happy to approve but I'll leave it to @white-gecko to finalise the PR since he's asked a question.
@white-gecko I did not see #570 and haven't played with epytext, but if that's useful I can add it to this PR. |
:-) |
It looks like in #569 it was determined that there isn't much epytext syntax remaining, so I think #570 can be closed outright. If we find syntax like that described in http://epydoc.sourceforge.net/fields.html, then we can revisit, but the likely solution would be to replace it to be consistent with the rest of RDFlib, rather than adding a Sphinx extension. |
Ah ok, so it is like PEP 257, then we should go for PEP 257. |
Was testing out #1007, and I don't think that was done correctly. I've built on it. Hopefully each individual commit is self-explanatory, but, to summarize:
.gitignore
so that they won't accidentally get readded.apidocs/
directory for continuity.docs/sphinx-requirements.txt
and an "extra" sopip install rdflib[docs]
will get you what you need.Expand for current output:
Replaces #1007.
Closes #938.