-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add sphinx.ext.apidoc
extension
#13333
base: master
Are you sure you want to change the base?
Conversation
A common use-case is that users simply want to point Sphinx towards a Python module, and have it generate documentation automatically. This is not possible currently, without a "pre-build" step of running the `sphinx-autogen` CLI. This PR adds `sphinx.ext.apidoc` as a sphinx extension, to incorporate the source file generation into the sphinx build. Co-authored-by: Adam Turner <[email protected]>
Feel free to push to the original PR branch in the future instead of opening a replacement PR, makes it easier to keep all review comments in the same place! |
Would you oppose splitting these out to one configuration option per default value? It's easier for typing and documentation to be more granular, but it is more verbose. This is also the approach taken by https://github.com/sphinx-contrib/apidoc. A |
so like yeh err it is a bit verbose, and annoying to code 😅 thinking out loud; would it not be nicer to more generally allow |
Purpose
A common use-case is that users simply want to point Sphinx towards a Python module, and have it generate documentation automatically.
This is not possible currently, without a "pre-build" step of running the
sphinx-autogen
CLI.This PR adds
sphinx.ext.apidoc
as a sphinx extension, to incorporate the source file generation into the sphinx build.https://sphinx--13333.org.readthedocs.build/en/13333/usage/extensions/apidoc.html#module-sphinx.ext.apidoc
References
sphinx.ext.apidoc
as an extension #12471sphinx.ext.apidoc
extension #13220