Upstream software project

python-docformatter

Utility to re-format docstrings per PEP 257

About python-docformatter

Utility to re-format docstrings per PEP 257

This project links 4 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

python-docformatter repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-docformatter: recorded package coverageDebian 12 (Bookworm)1 recordsopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-docformatter
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, opensuse-leap-15-6, opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Docformatter currently automatically formats docstrings to follow a subset of the PEP 257 conventions. Below are the relevant items quoted from PEP 257. - For consistency, always use triple double quotes around docstrings. - Triple quotes are used even though the string fits on one line. - Multi-line docstrings consist of a summary line just like a one-line docstring, followed by a blank line, followed by a more elaborate description. - The BDFL recommends inserting a blank line between the last paragraph in a multi-line docstring and its closing quotes, placing the closing quotes on a line by themselves. docformatter also handles some of the PEP 8 conventions. - Don't write string literals that rely on significant trailing whitespace. Such trailing whitespace is visually indistinguishable and some editors (or more recently, reindent.py) will trim them.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package python3-docformatter

    bookworm (Debian 12 (Bookworm)) (python): Formats docstrings to follow Python PEP 257 (Python 3)

    1.4-3: all

    Source: python-docformatter

openSUSE Leap 15.6

  1. Package python3-docformatter

    leap-15.6 (openSUSE Leap 15.6) (Development/Languages/Python): Utility to re-format docstrings per PEP 257

    1.1-bp156.3.2: noarch

    Source: python-docformatter

openSUSE Tumbleweed

  1. Package python313-docformatter

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Utility to re-format docstrings per PEP 257

    1.7.8-1.2: noarch

    Source: python-docformatter

  2. Package python314-docformatter

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Utility to re-format docstrings per PEP 257

    1.7.8-1.2: noarch

    Source: python-docformatter

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.