Docs
Coding
Python
Best Practice
pre-commit

pre-commit

TL;DR

Before committing any staged Python files, pre-commit automatically formats the code, validates compliance to PEP8, and performs different types of checking to keep the code and the project clean. This automatical process can greatly save our time on code formatting so that we can concentrate on code logic.

Basic pre-commit workflow (source: Automate Python workflow using pre-commits: black and flake8)

Basic pre-commit workflow (source: Automate Python workflow using pre-commits: black and flake8)

What is pre-commit?

pre-commit is a multi-language package manager for pre-commit hooks. You specify a list of hooks you want and pre-commit manages the installation and execution of any hook written in any language before every commit.

Quick start

  1. Install pre-commit package manager

    • pip

      pip install pre-commit

    • conda

      conda install -c conda-forge pre-commit

    Check if the installation is successful:

    pre-commit --version

    If successful, you can see the version information

  2. (Optional) Add pre-commit to requirements.txt

  3. Add a pre-commit configuration

    1. Create a file named .pre-commit-config.yaml in the root of the project

    2. Define hooks/plugins in .pre-commit-config.yaml (More see: Adding pre-commit plugins)

      You can generate a very basic configuration using pre-commit sample-config

  4. Install the git hook scripts (prerequisite: git is already initialized)

    pre-commit install

    Now pre-commit will run automatically on every git commit (usually pre-commit will only run on the changed files during git hooks).

  5. (Optional) Run pre-commit against all the files

    pre-commit run --all-files

Adding pre-commit plugins

Once you have pre-commit installed, adding pre-commit hooks/plugins to your project is done with the .pre-commit-config.yaml configuration file, which describes what repositories and hooks are installed.

The top-level of .pre-commit-config.yaml is a map. Among them, the most important key is repos, which is a list of repository mappings. For other keys see: .pre-commit-config.yaml - top level.

repos

The repository mapping tells pre-commit where to get the code for the hook from.

repothe repository url to git clone from
revthe revision or tag to clone at. (new in 1.7.0: previously sha)
hooksA list of hook mappings.

Example

repos:
-   repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v1.2.3
    hooks:
    -   ...

hooks

The hook mapping configures which hook from the repository is used and allows for customization.

  • The necessary key is id, telling which hook from the repository to use. Other keys are optional.

  • All optional keys will receive their default from the repository’s configuration.

Example

repos:
-   repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v1.2.3
    hooks:
    -   id: trailing-whitespace

Useful repos and hooks

We briefly introduce some important and useful hooks. For supported hooks, check the website of pre-commit.

pre-commit-hooks

Some out-of-the-box hooks for pre-commit.

Example

  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v4.0.1
    hooks:
      - id: check-added-large-files # Prevent giant files from being committed.
      - id: check-ast # Simply check whether files parse as valid python.
      - id: check-byte-order-marker
      - id: check-case-conflict # Check for files with names that would conflict on a case-insensitive filesystem like MacOS HFS+ or Windows FAT
      - id: check-docstring-first # Checks for a common error of placing code before the docstring.
      - id: check-json # Attempts to load all json files to verify syntax.
      - id: check-yaml # Attempts to load all yaml files to verify syntax.
      - id: end-of-file-fixer # Makes sure files end in a newline and only a newline.
      - id: trailing-whitespace # Trims trailing whitespace.
      - id: mixed-line-ending # Replaces or checks mixed line ending.

black

The black code formatter in Python is an “uncompromising” tool that formats your code in the best way possible.

Example

  - repo: https://github.com/psf/black
    rev: 20.8b1
    hooks:
      - id: black
        args:
          - --line-length=119

isort

isort is a Python utility / library to sort imports alphabetically, and automatically separated into sections and by type.

To allow customizations to be integrated into any project quickly, isort supports various standard config formats. Check the documentation for all supported formats. I personally prefer setup.cfg.

When applying configurations, isort looks for the closest supported config file, in the order files are listed below. You can manually specify the settings file or path by setting --settings-path from the command-line. Otherwise, isort will traverse up to 25 parent directories until it finds a suitable config file.

For projects that officially use both isort and black, it is recommended to set the black profile in a config file.

Example: setup.cfg

[isort]
multi_line_output = 3
include_trailing_comma = True
force_grid_wrap = 0
use_parentheses = True
line_length = 88
profile = black
Sometimes the skip options do not work well, to skip some file for some reasons, check: Action Comments.

flake8

flake8 is a command-line utility for enforcing style consistency across Python projects. It is a popular lint wrapper for python. Under the hood, it runs three other tools and combines their results:

A good practice to customized flake8 checking is to define custom configurations in setup.cfg and specify its path with --args in .pre-commit-config.yaml:

setup.cfg

[flake8]
max-line-length = 119
max-complexity = 11
ignore = C901, W503, W504, E203, F401

[isort]
multi_line_output = 3
include_trailing_comma = True
force_grid_wrap = 0
use_parentheses = True
line_length = 88
profile = black

and in .pre-commit-config.yaml

  - repo: https://github.com/PyCQA/flake8
    rev: 4.0.1
    hooks:
      - id: flake8
        args:
          - --config=setup.cfg

GitHub Gist

My personal pre-commit config for python projects.

Reference