Install yapf with Homebrew, apt, Nix, pacman

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• yapf
• yapf-diff

Project history

The Google-owned GitHub repository was created on 2015-03-18, and PyPI history shows public 0.1.x packages in April 2015. The README explicitly says YAPF is based on clang-format, developed by Daniel Jasper, and that its goal is to produce code as good as a programmer would write while following a style guide.

YAPF's design grew out of formatter culture rather than linter culture. Its README contrasts the project with tools that remove lint errors and emphasizes a configurable formatting engine with named styles such as pep8, google, yapf, and facebook plus many individual knobs. Later changelog entries show continued maintenance for newer Python syntax and packaging shifts, including the move away from lib2to3 toward blib2to3 for Python 3.11-era parsing.

Adoption history

YAPF became one of the main Python auto-formatters of the mid-2010s, especially for teams that wanted clang-format-style configurability instead of a single canonical layout. Its README documents editor integrations, recursive formatting, diff mode for CI checks, local style discovery, and ignore files, all of which match adoption through developer tooling, pre-submit checks, and editor save hooks.

The formatter's long-term place changed after Black popularized less-configurable formatting, but YAPF remained important where repositories wanted Google/Facebook-like styles, large configuration surfaces, or incremental compatibility with existing formatting policy.

How it is used

Typical CLI usage is `yapf -i file.py` for in-place formatting, `yapf -d` for a diff suitable for review or CI, and `yapf -r` for recursive directory formatting. The `yapf-diff` helper fits patch-oriented workflows by formatting only changed hunks.

Configuration is central to YAPF usage. The formatter searches local style files such as `.style.yapf`, `setup.cfg`, and `pyproject.toml`, supports predefined base styles, and offers many style options for projects that treat formatting as policy rather than taste.

Why package nerds care

YAPF matters because it represents the configurable branch of Python formatter history: closer to clang-format and gofmt in automation, but less doctrinaire than later formatters. In package collections it is a standard example of a developer tool whose value is mostly in repeatability, editor integration, and reducing style churn in diffs.

It also shows how Python tooling had to adapt as the language parser story changed. Maintaining a formatter across Python syntax releases is partly a packaging problem: the executable must track language versions, config formats, editor plugins, and CI behavior at the same time.

Timeline

• 2015-03-18: google/yapf repository is created on GitHub.
• 2015-04-07: PyPI records an early public 0.1.4 upload.
• 2023-06-13: YAPF 0.40.0 changelog notes Python 3.11 support and replacement of lib2to3 with blib2to3.
• 2023-09-22: YAPF 0.40.2 is published on PyPI.
• 2024-11-14: YAPF 0.43.0 is published on PyPI.

Related projects

• clang-format is the formatter model named by YAPF's README.
• autopep8 and pep8ify are older Python formatting tools contrasted by YAPF's documentation.
• Black is the later opinionated Python formatter often compared with YAPF in formatter choice discussions.

Sources

• https://api.github.com/repos/google/yapf
• https://github.com/google/yapf
• https://pypi.org/pypi/yapf/json
• https://raw.githubusercontent.com/google/yapf/main/CHANGELOG.md
• https://raw.githubusercontent.com/google/yapf/main/README.md