I'm trying to write an extension to make a version of autosummary that behaves something like a hybrid between the automodule directive (with :members:) and autosummary. That is, I want it to be like autosummary, but instead of explicitly specifying all of the members to make autosummary stub pages for, I want it to automatically do it for *all* of them.
The problem I'm running into is that it appears that autosummary's generation utility seems to be to look directly at the files for the autosummary directive rather than parsing the doctree and using nodes in the doctree to figure out what needs to be generated. I can probably adapt the internal logic in autosummary to do the same thing for an autogenerated list of members, but I want to make sure there isn't some way of doing this already hidden in autosummary before I undertake such a task. Also, if I can get this working, is it something that would be worth including as an addition option to autosummary, or is it better as a separate extension? -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
