Install flake8 with Homebrew, apt, pacman

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• flake8

Project history

The recorded release history begins with the 0.x series; the 0.6 release in February 2010 fixed McCabe metric handling, and 1.0 followed in November 2011 with complexity-checking changes. The project later moved under PyCQA, whose official repository describes flake8 as a tool that combines pycodestyle, pyflakes, mccabe, and plugins.

The 3.0.0 release in July 2016 was a major internal and documentation rewrite. Its notes say the project removed dependence on pep8/pycodestyle for file processing and plugin dispatch while keeping compatibility, added formatter entry points, improved plugin option registration, changed hook installation behavior, and rewrote documentation at flake8.pycqa.org.

Adoption history

flake8 became popular because it packaged several Python code-quality checks behind one command and one set of configuration files. The official plugin guide explicitly attributes much of its popularity to extensibility and notes that community plugins are typically distributed on PyPI.

In day-to-day Python packaging, flake8 is commonly installed into the same Python environment that should parse the target code. The docs warn that Flake8 is tied to the Python version on which it runs, because it must understand that version's syntax.

How it is used

The basic workflow is `flake8 path/to/code.py` or `flake8 path/to/code/`, optionally with selection and ignore flags for specific error codes. The user guide documents project configuration in `setup.cfg`, `tox.ini`, or `.flake8`, all using a `[flake8]` INI section.

Plugins extend checks and formatters. After installation, most plugins immediately start reporting their own codes, and some register additional command-line or configuration options.

Why package nerds care

flake8 matters to package nerds because it became the small, composable linting facade for a large slice of Python packaging: pycodestyle contributes E/W codes, PyFlakes contributes F codes, McCabe contributes C codes, and plugins add their own namespaces.

Its configuration-file search and plugin entry-point model made it easy for projects, tox environments, pre-commit hooks, and distribution packages to agree on one executable while still carrying local policy.

Timeline

• 2010: 0.6 release recorded in official release notes.
• 2011: 1.0 release changes default complexity-checking behavior.
• 2016: 3.0.0 rewrites documentation, file processing, plugin dispatch, and formatter extension points.
• 2020s: 7.x release series appears in the official release history.

Related projects

• pycodestyle supplies PEP 8 style checks and E/W error-code classes.
• PyFlakes supplies lint checks such as unused imports and F error codes.
• McCabe supplies complexity checks and C error codes.
• Third-party flake8 plugins distributed through PyPI add checks and formatters.

Sources

• https://flake8.pycqa.org/en/latest
• https://flake8.pycqa.org/en/latest/release-notes/index.html
• https://flake8.pycqa.org/en/latest/user/configuration.html
• https://flake8.pycqa.org/en/latest/user/using-plugins.html
• https://github.com/PyCQA/flake8