-
Notifications
You must be signed in to change notification settings - Fork 52
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
Sphinx Guidance? #141
Comments
Hi! As far as I know, none of the listed tools account for
You can make a "fake" module out of generated stubs by renaming all |
Thank you for the guidance, renaming is a great suggestion. Yes on tooling support; I did some checks with |
What we do is build the wheels in github actions, publish the wheels as an artifact, and then tell RTD to retrieve the correct wheel and install it -- at which point sphinx can do the things it normally does. It requires setting up a token to access the github API, but works great. |
I second @sizmailov's suggestion of renaming - in my own workflow I use the stub files for doc generation rather than the actual wheel because functions in a *.so file cannot be inspected, which means that some functionality of the sphinx autodoc extension does not work properly when using the actual package. I generate the stubs and rename them to *.py files in the CI workflow only for docs generation. |
Hi,
Thank you so much for this project!
I was reading up a bit and cannot find yet guidance on this:
Which extensions do people use to read stub-only
.pyi
files into Sphinx docs, e.g., for quick RTD builds?autoapi.extension
(sphinx-autoapi)?Are there a few example pybind11 projects you are aware of that build API docs purely from
.pyi
files?My workflow is as follows:
.pyi
stubs in CI, where I can run a long time (build pybind11 modules).pyi
stubs to the repoThe text was updated successfully, but these errors were encountered: