sphinx-linter 0.0.17

A lightweight Python linter for checking Sphinx docstrings.

sphinxlinter

A lightweight Python linter for Sphinx-style docstrings.
It validates structure, field consistency, and alignment between documentation and code.

---

Overview

Sphinx-style docstrings are widely used across Python projects, but existing tools such as pydocstyle, pydoclint, and ruff focus primarily on general docstring formatting, PEP257 compliance, and style enforcement.

It is designed to complement, not overlap with, these tools.
It targets Sphinx-specific field list conventions and performs semantic consistency checks that go beyond what other linters cover.

Specifically, it focuses on:

• 🧩 Enforces Sphinx-style field list formatting
• 🛠️ Ensures consistency between docstrings, signatures, and implementation
• 📐 Validates section order, duplication, and syntax of documented types and errors
• 📊 Generates concise, CI-friendly reports
• ⚙️ Provides a minimalist CLI for easy workflow integration
• 🐍 Uses only the Python standard library for full compatibility
• 🧼 Promotes clean, maintainable documentation

---

📦 Installation

Requires Python ≥ 3.9.

To install via pip, run:

pip install sphinx-linter

---

⚡ Quick Start

CLI Tool

After installation via pip, you can run the sphinxlinter command directly from your terminal.

Run on the current directory:

• Run in the current directory: sphinxlinter .
• Or use the short alias: spxl .

Run on specific files or directories:

spxl path/to/file.py path/to/package/

[!NOTE]

Directories are scanned recursively for .py files, ignoring virtual environments and cache folders.

Standalone Script

Alternatively, you can download the standalone script by clicking the following link and run it with Python:

python sphinxlinter.py path/to/source/

---

Command Line Usage

Argument / Option	Description
[FILES]	Files or directories to lint.
--help	Show help message and exit.
--enable	Enable specific rule codes (or ALL).
--disable	Disable specific rule codes (overrides --enable).
--ignore	Exclude directories (e.g. venv, .cache).
--statistics	Show per-rule violation counts.
--quiet	Suppress all output except summary.

---

Output Format

When violations are found, the tool outputs lines in the following format:

path/to/file.py:LINE-NUMBER: [CODE] Description of the violation.

[!TIP]

Use --quiet to suppress output except for statistics summary if --statistics is also set.

[!NOTE]

• Exit code 0 means no violations were found; exit code 1 indicates that violations were detected.
• The tool never modifies source files.

Categories:

• DOC0xx: Structure and formatting issues
• DOC1xx: Parameter issues
• DOC2xx: Return issues
• DOC3xx: Raises issues
• DOC4xx: Variable issues

---

Violation Codes

DOC0xx — Structure

Code	Description	Purpose
DOC001	Invalid docstring section	Detects unsupported Sphinx fields.
DOC002	Malformed section	Ensures valid field list syntax.
DOC003	Missing blank line after docstring	Improves readability.
DOC004	Missing blank line between summary and sections	Enforces structure consistency.
DOC005	Too many consecutive blank lines	Prevents unnecessary whitespace.
DOC006	Trailing empty lines	Keeps docstrings compact.
DOC007	Misplaced section	Enforces section order and grouping.
DOC008	One-line docstring should end with a period	Complies with PEP 257.
DOC009	Docstring must not use more than 3 double quotes	Promotes consistent quoting.
DOC010	Section definition contains invalid whitespace	Ensures proper formatting.
DOC011	Trailing non-empty lines after last section	Maintains clean endings.

---

[!NOTE]

DOC008: This rule differs from Ruff’s similar rule missing-trailing-period, which enforces a trailing period on the first line of both one-line and multi-line docstrings. By contrast, the rule DOC008 only enforces a trailing period on one-line docstrings, following the recommendation in PEP 257.

[!NOTE]

DOC009: Unlike Ruff triple-single-quotes, this rule only checks that multi-line docstrings do not start or end with more than three double quotes.

---

DOC1xx — Parameters

Code	Description	Purpose
DOC101	Parameter documented but not in signature	Detects undocumented or extra parameters.
DOC102	Invalid parameter type syntax	Enforces valid Python type hints.
DOC103	Parameter type already in signature	Avoids redundant type info.
DOC104	Parameter type mismatch with annotation	Ensures consistency with annotations.
DOC105	Duplicated parameter	Prevents repetition.

---

DOC2xx — Returns

Code	Description	Purpose
DOC201	Return documented but function has no return statement	Detects unnecessary return sections.
DOC202	Invalid return type syntax	Enforces valid type expressions.
DOC203	Return type already in signature	Avoids redundancy.
DOC204	Return type mismatch with annotation	Validates against function annotations.
DOC205	Duplicated return section	Prevents duplication.

---

DOC3xx — Raises

Code	Description	Purpose
DOC302	Invalid exception type syntax	Ensures valid Python exception syntax.
DOC305	Duplicated exception type	Prevents redundant entries.

---

DOC4xx — Variables

Code	Description	Purpose
DOC402	Invalid variable type syntax	Enforces valid Python type hints.
DOC403	Variable name contains invalid whitespace	Ensures valid identifiers.
DOC405	Duplicated variable	Prevents repetition.

---

How It Works

The tool statically analyzes Python source code using the built-in AST module:

1. Parses FunctionDef, AsyncFunctionDef, ClassDef, and Module nodes.
2. Extracts Sphinx-style docstring fields.
3. Validates structure, syntax, and consistency with annotations.

The tool prints findings to stdout and never modifies source files.

CI Integration:
Treat any output as a failure signal in your build pipeline.

---

🛠️ Development

To contribute to the project, you can run the following commands for testing and documentation:

First, ensure you have the latest version of pip:

python -m pip install --upgrade pip

Running Tests

pip install --group=test --upgrade # Install test dependencies, skip if already installed
python -m pytest tests/ # Run all tests
python -m pytest tests/ --cov # Run tests with coverage

Running Linter

pip install --group=lint --upgrade  # Install lint dependencies, skip if already installed
ruff check . # Run linter

🗒️ License

This project is licensed under the MIT license.