Pylint Per File Ignores

This pylint plugin will enable per-file-ignores in your project!

The project was initially created by christopherpickering.

Install

pip install pylint-per-file-ignores

Add to Pylint Settings

.pylintrc

[MAIN]
load-plugins =
    pylint_per_file_ignores

setup.cfg

[pylint.MASTER]
load-plugins =
    pylint_per_file_ignores

pyproject.toml

[tool.pylint.main]
load-plugins = [
    "pylint_per_file_ignores",
]

Usage

Add a list of patterns and codes you would like to ignore following <file-pattern>:<code1>,<code2>. The patterns are matched using globs. Newlines between codes are supported.

Prior to v2.0.0, pylint-per-file-ignores did not use globs but regex. When migrating, please check your configuration carefully.

Please note, that if two patterns applies the same files, the last configuration will be used.

.pylintrc

[MESSAGES CONTROL]
per-file-ignores =
  /folder_1/*:missing-function-docstring,W0621,W0240,C0115
  file.py:C0116,E0001

setup.cfg

[pylint.MESSAGES CONTROL]
per-file-ignores =
  /folder_1/*:missing-function-docstring,W0621,W0240,C0115
  file.py:C0116,E0001

pyproject.toml

[tool.pylint.'messages control']
per-file-ignores = [
    "/folder_1/*:missing-function-docstring,W0621,W0240,C0115",
    "file.py:C0116,E0001"
]

Please note, that for non-toml files newlines are important. For example, the following won't parse as expected

[pylint.MESSAGES CONTROL]
per-file-ignores =
  /folder_1/*:missing-function-docstring,
    missing-class-docstring

Development

This project uses uv. To install uv, and setup a venv for development, use:

python3.14 -m venv venv && \
    source venv/bin/activate && \
    pip install uv && uv sync --all-groups && \
    deactivate  && \
    rm -rf venv/

This will create a temporary venv, install uv to bootstrap the project .venv, and remove the temporary venv again. Then use source .venv/bin/activate to activate your venv.

Build and Publish

Execute the release action with the proper version.

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2026 SAP SE or an SAP affiliate company and pylint-per-file-ignores contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.