pydocformatter
pydocformatter is a rule-based linter and source formatter for Python docstrings and comments. Its pydocfmt command reports precise rule findings, applies fixes when source changes are safe, and leaves ambiguous or content-creating decisions to the author.
pydocformatter handles documentation and comment source; it does not format ordinary Python expressions or statements. Use it alongside Ruff or another general Python formatter.
What it does
- Reflows docstring and comment prose, normalizes source layout, and preserves supported structured regions such as doctests, code fences, directives, lists, tables, and block quotes.
- Understands PEP 257, Google, NumPy, and reStructuredText docstring conventions, including semantic sections and documented parameters, returns, yields, exceptions, and attributes.
- Formats standalone and trailing comments while protecting recognized type-checker, linter, formatter, security, and IDE directives.
- Selects independently documented PCF comment rules and PDF docstring rules, with per-rule diagnostics and explicit fix availability.
- Uses Ruff-style configuration, file discovery, selectors, per-file ignores, fixability controls, source suppressions, and inspection commands.
- Preserves evaluated docstring values for source-literal rewrites that require semantic equivalence, while content-formatting rules may intentionally change docstring whitespace, and avoids automatic changes when the intended source rewrite or missing documentation cannot be inferred safely.
Documentation and help
The documentation site is the complete user guide and reference. These links go directly to the relevant help:
| Need | Resource |
|---|---|
| Install and complete a first run | Tutorial and Installation |
| Configure pydocfmt | Configuration and generated Settings |
| Configure Ruff alongside pydocformatter | Ruff rule links |
| Understand a rule or browse available rules | Rules or pydocfmt rule RULE |
| Choose or inspect active, ignored, per-file, and fixable rules | Rule selection and pydocfmt check --show-rules |
| Understand checking, fixing, suppressions, and file discovery | Checking, Formatting, Rule suppressions, and File selection |
| Add pre-commit, CI, or editor workflows | Integrations |
| Resolve common questions | FAQ, pydocfmt --help, pydocfmt check --help, and pydocfmt config SETTING |
| Report a bug or propose a change | GitHub Issues |
Installation
pydocformatter officially supports CPython 3.11 or newer. Compatibility with PyPy and GraalPy is intended but is not currently verified or guaranteed. LibCST's native parser does not publish binary wheels for these implementations, so installation may require an unverified source build. Jython and IronPython are unsupported. Ubuntu 20.04 and newer and macOS 14 and newer are supported. Other POSIX Linux systems, including musl-based distributions, receive best-effort support. Native Windows and WSL are unsupported.
Git is conditionally required for the default gitignore-aware recursive file discovery inside Git worktrees. Install Git or pass --no-respect-gitignore when that filtering is not wanted.
Add pydocformatter to a project as a development dependency with uv:
uv add --dev pydocformatter
uv run pydocfmt --version
To install the command independently of a project environment:
uv tool install pydocformatter
See Installation for pip, pipx, and Git pre-commit alternatives. If pydocfmt is already available on PATH, omit uv run from the commands below.
Quick start
Run pydocformatter from a project root to check discovered Python files without changing them:
uv run pydocfmt check
Preview automatic fixes as a unified diff, or apply them in place:
uv run pydocfmt check --diff
uv run pydocfmt check --fix
Pass files or directories to limit the run, for example uv run pydocfmt check src tests. With no paths, pydocformatter checks the current directory. Check mode returns a nonzero exit status when it finds rule violations or operational errors, which makes the same command suitable for CI.
Persistent cache
pydocformatter caches strict clean proofs for selected disk files by default. A warm hit still discovers the file and verifies its complete raw contents, settings, selected rules, implementation, and package-path semantics, but skips UTF-8 decoding, LibCST parsing, and rule execution. The cache stores hashes and metadata only, never source text or diagnostics. Cache failures fall back to normal analysis without changing status; a missing or non-directory immediate cache parent also emits one warning.
The default cache is .pydocfmt_cache below the auto-discovered project root. Disable reuse for diagnostics or untrusted restored cache data, inspect opt-in counters, or remove only pydocfmt-owned cache data with:
uv run pydocfmt check --no-cache
uv run pydocfmt check --cache-stats
uv run pydocfmt clean
uv run pydocfmt clean --cache-dir PATH
Use cache-dir or --cache-dir PATH to choose another location. pydocformatter may create that directory, but its immediate parent must already exist as a directory; it does not create missing ancestors. An owned run cache directory below a checked tree is pruned automatically during file discovery; a non-empty unowned directory receives normal include and exclude handling. The persistent cache reference documents invalidation, mode reuse, storage, cleanup, failures, security, statistics, and performance expectations.
Configuration
Place project settings in pyproject.toml. A small configuration might specify only the shared line length and the project's docstring convention:
[tool.pydocfmt]
line-length = 88
[tool.pydocfmt.docstring]
convention = "google"
Inspect the resolved configuration, discovered files, and active rules before changing source:
uv run pydocfmt check --show-settings
uv run pydocfmt check --show-files
uv run pydocfmt check --show-rules
uv run pydocfmt rule PDF101
Use uv run pydocfmt config to list every setting, or pass a setting name such as uv run pydocfmt config line-length for focused help. The documentation table above links the full configuration, settings, rule-selection, and Ruff-compatibility references.
Examples
In each example, [settings] or Settings (when present) shows the relevant pydocformatter settings used, including pertinent defaults. [input] or Before shows the original source, [output] or After shows the source after automatic fixes, and [findings] or Findings shows the diagnostics that remain afterward (not auto-fixable).
Reflow with human-authored documentation left to do
This function has ordinary long prose and a partially documented Google-style signature. pydocformatter can reflow the prose, but it cannot decide how the summary should be shortened or invent documentation for default_role.
[settings]
line-length = 88
docstring-convention = "google"
[input]
"""User configuration helpers."""
def load_user(path, default_role):
"""Loads a user record from disk and returns normalized settings for the application with predictable defaults.
Args:
path: Path to the user configuration file.
"""
# Keep the fallback role in the returned record so callers can handle incomplete configuration files consistently across environments.
return {"path": path, "role": default_role}
[output]
"""User configuration helpers."""
def load_user(path, default_role):
"""Loads a user record from disk and returns normalized settings for the application
with predictable defaults.
Args:
path: Path to the user configuration file.
"""
# Keep the fallback role in the returned record so callers can handle incomplete
# configuration files consistently across environments.
return {"path": path, "role": default_role}
[findings]
PDF203: Lines 5-6: Docstring summary spans 2 lines and does not fit on one line
PDF500: Line 4: Function parameter 'default_role' is missing docstring documentation
PDF101 and PCF000 apply the safe wrapping changes. PDF203 and PDF500 remain as diagnostic-only findings for the author to resolve, including in particular that the docstring summary line now does not fit on one line, when in general it should.
Trailing comments and stale suppressions
This retry helper contains an overlong trailing explanation and a suppression that no longer suppresses anything. Moving the explanation and removing the obsolete directive are separate policy decisions, so the relevant rules expose them separately.
[settings]
line-length = 72
[input]
"""Retry policy helpers."""
def _retry_delay(attempt):
# pydocfmt: ignore[PCF000]
# Keep retry delays bounded.
delay = min(2**attempt, 60)#Cap exponential backoff so temporary failures do not stall a worker indefinitely.
return delay
[output]
"""Retry policy helpers."""
def _retry_delay(attempt):
# pydocfmt: ignore[PCF000]
# Keep retry delays bounded.
# Cap exponential backoff so temporary failures do not stall a
# worker indefinitely.
delay = min(2**attempt, 60)
return delay
[findings]
PCF101: Line 5: Suppression selector 'PCF000' did not suppress any findings
PCF001 normalizes the trailing-comment delimiter before PCF002 moves and wraps the explanation. The blank line preserves separation from the independently authored comment above it. PCF101 reports the stale suppression but deliberately does not delete it.
Using pydocformatter with Ruff
pydocformatter is intended to own docstring and comment formatting where its rules overlap with Ruff. Align shared settings such as indentation and line endings, and disable Ruff rules that would enforce the same docstring or comment policy. The Ruff rule links page provides a paired configuration and rule-by-rule compatibility mapping.
Contributing
See Contributing for the development environment, rule implementation workflow, documentation pipeline, and pull request checks. Project history and current unreleased changes are recorded in the Changelog.
License
pydocformatter is licensed under the GNU General Public License v3.0 or later.
Acknowledgments
pydocformatter draws inspiration from pyformatter, docformatter, and established Python formatting tools such as Ruff.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file pydocformatter-1.1.0.tar.gz.
File metadata
- Download URL: pydocformatter-1.1.0.tar.gz
- Upload date:
- Size: 983.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"20.04","id":"focal","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f28e99f201d3988d8aae75d696f35b77fda4383caaff9da453f387f6ec5e8342
|
|
| MD5 |
7252f1a565d6e11671a6ac3d2294dad1
|
|
| BLAKE2b-256 |
a963ef183f997f898f51c27a66fe97e13b557a669d496b59e25e842ce25252d5
|
File details
Details for the file pydocformatter-1.1.0-py3-none-any.whl.
File metadata
- Download URL: pydocformatter-1.1.0-py3-none-any.whl
- Upload date:
- Size: 768.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"20.04","id":"focal","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
5fdb480ec3a0eeafa85f912fb043ad5c4bd930756de96e46eac71673658884e8
|
|
| MD5 |
6bcb57cc927668b237eb5c1273290b65
|
|
| BLAKE2b-256 |
729adc696245dbf6489de84521a9b45a87258a3f720a98cc925b515ba26b5a28
|