pyDocusaurus: Convert your Python docstrings to Docusaurus Documentation
This package is inspired by Sphinx, which is usually thought of as the "official" solution for auto-generated Python documentation. According to Sphinx's documentation, the automatic generation can be described as:
Generate API documentation for Python, C++ and other software domains, manually or automatically from docstrings, ensuring your code documentation stays up-to-date with minimal effort.
——Sphinx
Overall, this package offers similar functionalities to Sphinx. It goes through the docstrings in the whole package and reorganizes them as an automatically generated API document. However, pyDocusaurus is not an extension of Sphinx, because
- Sphinx is old. It was designed in an era when typing or type hints were not part of the Python standard library (STL). Therefore, Sphinx needs to infer the types from the docstrings. In modern Python code, this feature is redundant.
- Sphinx is essentially proposed for reStructuredText (rst). Certainly, it supports Markdown with specific extensions. However, the Markdown features, especially those related to variable types, are not well integrated with the automatically generated API documents. Users may still suffer a lot of rst code in the generated document.
- Limited by the old-school template, Sphinx does not produce a "modern" website.
Essentially, this package will produce a "patch" for a Docusaurus project. Like Sphinx, pyDocusaurus will go through the whole package and convert the docstring into a Docusaurus-compatible API document, while requiring minimal modifications when integrating the auto-generated document with an existing Docusaurus project (e.g., an existing tutorial site).
1. Install
Intall the latest released version of this package by using the PyPI source:
python -m pip install pydocusaurus
2. Usage
A simple usage is to use the CLI directly:
python -m pydocusaurus render-doc <package-name> -o <out-dir> -u <user-name>
It allows customizations by adding CLI options. To find the details, review the documentation of this project or call
python -m pydocusaurus render-doc --help
pyDocusaurus can also be called by Python codes, for example:
from pydocusaurus import render_package_as_mdx
import any_package
pydocusaurus.render_package_as_mdx(
pydocusaurus, out_dir=out_dir, package_info="username"
)
3. Documentation
Check the documentation to find more details about the examples and APIs.
https://cainmagi.github.io/pydocusaurus/
4. Contributing
5. Changelog
See Changelog.md 📖
Release files for pydocusaurus 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pydocusaurus-1.0.1.tar.gz | 2.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydocusaurus-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 MB
Release files / pydocusaurus-1.0.1.tar.gz
| Download URL | pydocusaurus-1.0.1.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ba721c89b74c4f66ed6f59df595b793b8278ba2c22ca667a451eaed6fbe95ca
|
|
BLAKE2b-256 checksum How to use checksums |
891331b01a34fdb728ac4819e6746a23c40411243cdf62d404509cdea800d13c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 20, 2026.
Transparency logRelease files / pydocusaurus-1.0.1-py3-none-any.whl
| Download URL | pydocusaurus-1.0.1-py3-none-any.whl |
|---|---|
| Size | 98.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2a601fec04332e109195da92cb75fecb4c38d68e0cf2b8bf82c1a735c691ef4
|
|
BLAKE2b-256 checksum How to use checksums |
04cfba31e3038241051591f2ea5e7a6f2de73c99b21ada98a8ffa7d0316299ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 20, 2026.
Transparency log