📝 A Python library package which bridges the gap between rich annotations and automatic documentation generation with configurable renderers and support for reusable fragments.
Key Features ⭐
🔄 Docstring Generation: Generation of docstrings for modules, classes, functions, and methods via introspection with fine-grained control.
🧩 Fragment System: Reusable documentation snippets for consistent terminology across projects.
🏷️ Annotation Metadata: Extraction and inclusion of metadata from annotations into generated docstrings.
🔌 Extensible Architecture: Custom renderers, attribute visibility rules, and introspection limiters.
📖 Sphinx-Compatible Output: Render reStructuredText docstrings that work with Sphinx Autodoc out of the box.
🎨 Configurable Renderers: Ability to extend with other renderers as desired.
Installation 📦
Method: Install Python Package
Install via uv pip command:
uv pip install dynadoc
Or, install via pip:
pip install dynadoc
Examples 💡
Please see the examples directory.
Function Documentation:
import dynadoc
from typing import Annotated
@dynadoc.with_docstring( )
def process_api_data(
endpoint: Annotated[ str, dynadoc.Doc( "API endpoint URL to query" ) ],
timeout: Annotated[ float, dynadoc.Doc( "Request timeout in seconds" ) ] = 30.0,
) -> Annotated[ dict, dynadoc.Doc( "Processed API response data" ) ]:
''' Process data from API endpoint with configurable timeout. '''
return { }
Which will be turned into the following docstring on the function by the default renderer:
Process data from API endpoint with configurable timeout.
:argument endpoint: API endpoint URL to query
:type endpoint: str
:argument timeout: Request timeout in seconds
:type timeout: float
:returns: Processed API response data
:rtype: dict
Module Documentation:
Document all annotated attributes in current module:
import dynadoc
dynadoc.assign_module_docstring( __name__ )
Contribution 🤝
Contribution to this project is welcome! However, it must follow the code of conduct for the project.
Please file bug reports and feature requests in the issue tracker or submit pull requests to improve the source code or documentation.
For development guidance and standards, please see the development guide.
More Flair
Metadata
Release files for dynadoc 1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dynadoc-1.4.tar.gz | 28.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dynadoc-1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.4 kB
Release files / dynadoc-1.4.tar.gz
| Download URL | dynadoc-1.4.tar.gz |
|---|---|
| Size | 28.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbfd5fd65e0b52dbbf7706b13b12a56a60185b919160ae5a461e7624ef6a9489
|
|
BLAKE2b-256 checksum How to use checksums |
0cfe2cb26453c6a50c1303f50ab1a6e5cc9c06b14bf0b3aa1914f6c5c21331bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2025.
Transparency logRelease files / dynadoc-1.4-py3-none-any.whl
| Download URL | dynadoc-1.4-py3-none-any.whl |
|---|---|
| Size | 37.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26f2a692ad97ddbc48183667c493f923d3328d06e4894793770bfc09c5130fff
|
|
BLAKE2b-256 checksum How to use checksums |
eeef38b621893e9bf3e8a755593a7a84f0d12a4a16de8f45adb62f4e95d66923
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2025.
Transparency log