Skip to content
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

Closed
maikelmeyers opened this issue Sep 14, 2017 · 5 comments
Closed

Autosummary extension has many deficits for proper using #4058

maikelmeyers opened this issue Sep 14, 2017 · 5 comments
Labels
Milestone

Comments

@maikelmeyers
Copy link

maikelmeyers commented Sep 14, 2017

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:

  • members
  • functions
  • classes
  • exceptions
  • methods
  • attributes

I miss the following variables for having the ability to fully automize the documentation:

  • modules
  • packages (sub packages)
  • module-level variables
  • class attributes
  • instance attributes
  • inherited class attributes
  • inherited instance attributes
  • methods
  • inherited methods
  • static methods
  • inherited static methods

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

@jorisvandenbossche
Copy link
Contributor

FYI, I opened a PR to properly fix #3900 (so to make sure also attributes are available again in the autosummary template): #4247

@tk0miya
Copy link
Member

tk0miya commented Jan 30, 2018

Fixed by #4247.
Thank you for reporting

@tk0miya tk0miya closed this as completed Jan 30, 2018
@tk0miya tk0miya added this to the 1.7 milestone Jan 30, 2018
@jorisvandenbossche
Copy link
Contributor

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).

@tk0miya
Copy link
Member

tk0miya commented Jan 30, 2018

oh, I'd misunderstood. Thanks,

@tk0miya tk0miya reopened this Jan 30, 2018
@tk0miya tk0miya added type:proposal a feature suggestion and removed type:bug labels Jan 30, 2018
@tk0miya tk0miya modified the milestones: 1.7, some future version Jan 30, 2018
@MagSec-Arts
Copy link

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.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants