Skip to main content

pyDocusaurus: Convert your Python docstrings to Docusaurus Documentation

Banner

GitHub release (latest SemVer) GitHub all releases GitHub PyPI - Downloads

GitHub Actions (Build) GitHub Actions (Release)

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

  1. 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.
  2. 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.
  3. 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

See CONTRIBUTING.md 📖

5. Changelog

See Changelog.md 📖

Release files for pydocusaurus 1.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pydocusaurus 1.0.2
File Size Uploaded
pydocusaurus-1.0.2.tar.gz 2.3 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for pydocusaurus 1.0.2
File Interpreter ABI Platform
pydocusaurus-1.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 2.4 MB

Release files / pydocusaurus-1.0.2.tar.gz

Download URL pydocusaurus-1.0.2.tar.gz
Size 2.3 MB
Tags Source
SHA-256 checksum
How to use checksums
9e1f8987f4e2d2840bedf9b9f31263a11cafab98a75d95f136f6a8347b05464d
BLAKE2b-256 checksum
How to use checksums
6955686aed0230a28c66d7a3dfe9cf5ac999b95ba302a4009095c397de055ff0
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 26, 2026.

Transparency log

Release files / pydocusaurus-1.0.2-py3-none-any.whl

Download URL pydocusaurus-1.0.2-py3-none-any.whl
Size 98.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7c83daa4c0aa5642a87b78a1157af5ff17b11d97b79ac177aa84fe157fd761c6
BLAKE2b-256 checksum
How to use checksums
25eaf004d9c3a1c244a572ace603c66a460c82c7cde2fcfbdffb0bf70c69a5e0
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 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.2 This release

2 release files

1.0.1

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page