Extending your autodoc API docs with a summary
docs |
|
|---|---|
tests |
|
package |
Welcome! This sphinx extension provides some useful extensions to the Sphinxs autodoc extension. Those are
It creates a Table of Contents in the style of the autosummary extension with methods, classes, functions and attributes
As you can include the __init__ method documentation for via the autoclass_content configuration value, we provide the autodata_content configuration value to include the documentation from the __call__ method
You can exclude the string representation of specific objects. E.g. if you have a large dictionary using the not_document_data configuration value.
See the Documentation on Readthedocs for more details.
Installation
Simply install it via pip:
$ pip install autodocsumm
Local development
Use pip on the source on GitHub:
$ pip install .
Requirements
The package only requires Sphinx to be installed. It has been tested for versions higher than 1.3.
Quickstart
In order to activate the autodocsumm extension, you have to list it in your conf.py:
extensions = [
'sphinx.ext.autodoc',
...,
'autodocsumm',
]
Once this is done, you can use the :autosummary: option for autodoc directives to generate a table at the top, e.g.:
.. automodule:: my.awesome.module
:autosummary:
Optionally, you can make autodocsumm active by default for all autodoc directives by adding in conf.py:
autodoc_default_options = {
'autosummary': True,
}
Disclaimer
Copyright 2016-2019, Philipp S. Sommer
Copyright 2020-2021, Helmholtz-Zentrum Hereon
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Metadata
Release files for autodocsumm 0.2.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| autodocsumm-0.2.15.tar.gz | 46.7 kB | Without provenance | Details for autodocsumm-0.2.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| autodocsumm-0.2.15-py3-none-any.whl | Python 3 | none | any | Details for autodocsumm-0.2.15-py3-none-any.whl |
Total release size: 61.5 kB
Release files / autodocsumm-0.2.15.tar.gz
| Download URL | autodocsumm-0.2.15.tar.gz |
|---|---|
| Size | 46.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eaf431e7a5a39e41a215311173c8b95e83859059df1ccf3b79c64bf3d5582b3c
|
|
BLAKE2b-256 checksum How to use checksums |
46b7f28dea12fae1d1ad1e706f5cf6d16e8d735f305ebee86fd9390e099bd27d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / autodocsumm-0.2.15-py3-none-any.whl
| Download URL | autodocsumm-0.2.15-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbe6fabcaeae4540748ea9b3443eb76c2692e063d44f004f67c424610a5aca9a
|
|
BLAKE2b-256 checksum How to use checksums |
ca3d4357a0f685c0a2ae7132ac91905bec565e64f9ba63b079f7ec5da46e3597
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for autodocsumm 0.2.15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.