-
-
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
Autosummary extension has many deficits for proper using #4058
Labels
Milestone
Comments
This was referenced Nov 14, 2017
Fixed by #4247. |
I am not the original reporter of the issue, but to me it seems that his enhancement request was more broad than what #4247 fixed (expose more variables to autosummary). |
oh, I'd misunderstood. Thanks, |
I'm working on a recursive auto summary to cover packages, sub-modules and sub-packages. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First to mention is that the bug found in #3900 is not really fixed, because the same applies to using class attributes
{{ attributes }}
in the templates. Autosummary does not find attributes anymore. Also the fix that was done for this in b3e0e29 is maybe not a good solution because{{ methods }}
now returns also all inherited methods of a class.Autosummary with it's templates is a really good solution for auto-documenting a library package without the need for any hand-written ResT file except the master-doc. But at the moment the available variables in the templates do not have enough granularity to achieve this. Beside of the available variables:
I miss the following variables for having the ability to fully automize the documentation:
With this variables it would be possible to walk recursively thru a package with 3 templates (packages.rst, modules.rst and class.rst). Especially the modules and packages variables would be important for this). And it would give us the full freedom for the layout of a package- module, and class- page. In example I could write my own headers in between the different groups of members inside the summary or in the details section because this variables mirror the granularity which we have with the autodoc directives.
Environment info
OS: Windows 10
Python version: 2.7
Sphinx version: 1.6.4
The text was updated successfully, but these errors were encountered: