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: option for all modules of a package #248

Closed
shimizukawa opened this issue Jan 2, 2015 · 3 comments
Closed

autosummary: option for all modules of a package #248

shimizukawa opened this issue Jan 2, 2015 · 3 comments
Labels
extensions type:enhancement enhance or introduce a new feature
Milestone

Comments

@shimizukawa
Copy link
Member

shimizukawa commented Jan 2, 2015

Like in this example:

.. autosummary::
   :toctree: generated/

   MaskedArray.base
   MaskedArray.ctypes
   MaskedArray.dtype
   MaskedArray.flags

one currently has to explicitly state the modules that should be documented by autosummary.

Please add option to automatically create stub files for all files in a package:

coule be like:

.. autosummary::
   :toctree: generated
   :nosignatures:
   :fullpackage: mypackage_toplevel_dir

This should then automatically include all modules in teh package "mypackage_toplevel_dir".

P.S.: I hope that this is not a misunderstanding or misconfiguration on my side. maybe this is already implemented?


@shimizukawa shimizukawa added this to the 1.x milestone Jan 2, 2015
@shimizukawa shimizukawa added type:enhancement enhance or introduce a new feature extensions labels Jan 2, 2015
@shimizukawa
Copy link
Member Author

From jasongrout on 2014-08-23 05:03:39+00:00

FYI, the astropy automodsumm has functionality something like this (see https://github.com/astropy/astropy-helpers/blob/master/astropy_helpers/sphinx/ext/automodsumm.py). It looks like sphinxydoc might be something good to look at too from #317 (see https://github.com/Ciantic/sphinkydoc)

@shimizukawa shimizukawa modified the milestones: 1.4, 1.x Feb 15, 2015
@shimizukawa shimizukawa modified the milestones: 1.5, 1.4 Mar 6, 2016
@shimizukawa shimizukawa modified the milestones: 1.6, 1.5 Oct 15, 2016
@tk0miya tk0miya modified the milestones: 1.7, 1.6 Apr 15, 2017
@maikelmeyers
Copy link

Is this still not implemented? I would like to see this feature.

@tk0miya tk0miya modified the milestones: 1.7, 1.8 Jan 5, 2018
@tk0miya tk0miya modified the milestones: 1.8.0, 2.0 Jul 29, 2018
@tk0miya tk0miya modified the milestones: 2.0.0, 2.1.0 Feb 5, 2019
@tk0miya tk0miya modified the milestones: 2.1.0, 2.2.0 Jun 2, 2019
@tk0miya tk0miya modified the milestones: 2.2.0, 2.3.0 Aug 18, 2019
@ben-spiller
Copy link

+1

Would be best as a general capability for autosummary to include/exclude members (whether members of a module or a class/exception), similar to how automodule/autoclass work.

e.g.

.. autosummary:: MyModuleOrClass
  :members:
  :private-members:
  :inherited-members:
  :exclude-members: not_this_one

We already have logic for getting the members of a module. Hopefully we can find some way to also reuse the autodoc code for include/excludes for autosummary.

@tk0miya tk0miya modified the milestones: 2.3.0, 2.4.0 Dec 8, 2019
@tk0miya tk0miya modified the milestones: 2.4.0, 3.0.0 Feb 7, 2020
@tk0miya tk0miya removed this from the 3.0.0 milestone Mar 14, 2020
@tk0miya tk0miya added this to the 3.1.0 milestone Mar 14, 2020
@tk0miya tk0miya closed this as completed Apr 22, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
extensions type:enhancement enhance or introduce a new feature
Projects
None yet
Development

No branches or pull requests

4 participants