Install darker with Homebrew

Project links

• Homepage

Commands and aliases

• darker

Project history

The README explains Darker as a response to a common adoption problem for Black: teams often want consistent formatting without one large repository-wide reformat. Darker compares revisions, formats with Black or another supported formatter, and writes back only the changed regions.

Adoption history

Darker's official docs document installation from PyPI, conda-forge availability, editor integrations, pre-commit usage, and a GitHub Action. The changelog records early 2020 releases, a 1.0.0 release in July 2020, conda-forge availability in 1.2.2, support for plain directories in 1.4.0, and a 3.0.0 release that added Ruff formatter support while moving linting to Graylint.

How it is used

Users typically run darker on files or directories inside a Git repository, optionally selecting a revision range, showing a diff, or configuring behavior through pyproject.toml under tool.darker.

Why package nerds care

Darker matters to Python package maintainers because it is about incremental formatter adoption: it reduces formatting churn in old codebases while still letting projects standardize on tools such as Black, Ruff, isort, flynt, and pyupgrade.

Timeline

• 2020: 0.1.0 and 1.0.0 were released.
• 2020: 1.2.2 added conda-forge availability.
• 2022: 1.4.0 added support for plain directories outside Git repositories.
• 2025: 3.0.0 added Ruff formatter support and changed default formatter dependencies.

Related projects

• The README points to Black, Ruff, isort, flynt, pyupgrade, pytest-darker, Graylint, pre-commit, and the Darker GitHub Action as adjacent tools and integrations.

Sources

• https://github.com/akaihola/darker
• https://github.com/akaihola/darker/blob/master/CHANGES.rst
• https://github.com/akaihola/darker/releases