Skip to main content

A flake8 plugin that validates the formatting of Google-style docstrings. The name is the museum-wall label affixed to the thing it describes: short, fixed-form explanatory text, checked for shape, bound to the artifact it annotates.

Install

pip install placard

placard registers itself with flake8 via the flake8.extension entry point. Once installed, flake8 discovers it automatically; no extra configuration is needed to start emitting PLC codes.

What it checks

placard does one job: given a docstring that exists, check that it is shaped the way the Google style guide demands. It does not decide whether a docstring should exist, and it does not check whether the docstring’s contents are true about the code.

Code

Band

Rule

PLC101

summary

Summary line is empty

PLC102

summary

Summary line does not end with a period

PLC103

summary

Summary line restates the function signature

PLC104

summary

Multi-line docstring has no blank line after summary

PLC201

section

Unrecognized section header

PLC202

section

Recognized section header with incorrect case

PLC203

section

Recognized section header missing its trailing colon

PLC204

section

Section header has trailing content after the colon

PLC301

args

Args: entry is not in name: description form

PLC302

args

Args: section is present but empty

Recognized section headers: Args:, Attributes:, Raises:, Returns:, Yields:. Attributes: is included because Google style uses it in class docstrings to document instance attributes (e.g. dataclass fields), using the same name: description shape as Args: entries.

Types belong in the signature

placard requires Args: entries in the bare name: description form and rejects name (type): description. Every consumer of a docstring that cares about types already has the signature – IDEs, help(), Sphinx autodoc, mkdocstrings, pydoc – so a parenthesized type in the docstring duplicates information already visible an inch above, with the added cost of having to stay in sync.

This is the one place placard is more opinionated than the published Google spec, which calls both forms canonical. Projects that prefer the typed form can # noqa: PLC301 on the entries that use it.

Works with pydoclint

Two tools, one flake8 invocation, no overlap:

  • placard (PLC) – is the docstring shaped correctly?

  • pydoclint (DOC) – does the docstring agree with the code?

A lowercase args: with a ragged body is correct-by-pydoclint, wrong-by-placard. A perfectly formatted Args: block missing half the parameters is correct-by-placard, wrong-by-pydoclint. The prefixes differ, so the two compose cleanly in one flake8 run.

A placard-aligned pydoclint invocation:

pydoclint \
    --style=google \
    --skip-checking-short-docstrings=False \
    --arg-type-hints-in-docstring=False \
    --check-return-types=False \
    --check-yield-types=False \
    src/

--skip-checking-short-docstrings=False makes pydoclint reject description-only docstrings on functions that take arguments; the remaining flags align with placard’s opinion that types belong in the signature, not the docstring.

Release files for placard 2026.5.30.83589

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

Source distribution (sdist)

Source distribution for placard 2026.5.30.83589
File Size Uploaded
placard-2026.5.30.83589.tar.gz 11.7 kB Details

Built distribution (wheel)

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

Total release size: 23.1 kB

Release files / placard-2026.5.30.83589.tar.gz

Download URL placard-2026.5.30.83589.tar.gz
Size 11.7 kB
Tags Source
SHA-256 checksum
How to use checksums
68c2fe3202594dc6972a15f37585c0ede02e0b3a9a66436e4d493e1d796b15ed
BLAKE2b-256 checksum
How to use checksums
b390c988cd22678338b079ccf4c7ca00b4118ae470d4c1530b6cac2ea782de53
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 May 30, 2026.

Transparency log

Release files / placard-2026.5.30.83589-py3-none-any.whl

Download URL placard-2026.5.30.83589-py3-none-any.whl
Size 11.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a954b1a26e67092f6ad26f7403a6ac0b78616aa0c3eb445ab63ad23b45adee7f
BLAKE2b-256 checksum
How to use checksums
73b0b1e06e596ec51343d59bceac4e3116e8fd5c40b59d99d54516a1cd5b717a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 May 30, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2026.5.30.83589 This release

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