The Pylint linter for Python code (https://www.pylint.org/).
Don't use Pylint when running `./pants lint`
Arguments to pass directly to Pylint, e.g. `--pylint-args="--ignore=foo.py,bar.py --disable=C0330,W0311"`
Requirement string for the tool.
--pylint-extra-requirements="['<str>', '<str>', ...]"
Any additional requirement strings to use with the tool. This is useful if the tool allows you to install plugins or if you need to constrain a dependency to a certain version.
The console script for the tool. Using this option is generally preferable to (and mutually exclusive with) specifying an --entry-point since console script names have a higher expectation of staying stable across releases of the tool. Usually, you will not want to change this from the default.
The entry point for the tool. Generally you only want to use this option if the tool does not offer a --console-script (which this option is mutually exclusive with). Usually, you will not want to change this from the default.
Path to `pylintrc` or alternative Pylint config file
--pylint-source-plugins="[<target_option>, <target_option>, ...]"
An optional list of `python_library` target addresses to load first-party plugins.
You must set the plugin's parent directory as a source root. For example, if your plugin is at
build-support/pylint/custom_plugin.py, add 'build-support/pylint' to
pants.toml. This is necessary for Pants to know how to tell Pylint to discover your plugin. See https://www.pantsbuild.org/v2.4/docs/source-roots
You must also set
load-plugins=$module_name in your Pylint config file, and set the
[pylint].config option in
While your plugin's code can depend on other first-party code and third-party requirements, all first-party dependencies of the plugin must live in the same directory or a subdirectory.
To instead load third-party plugins, set the option
[pylint].extra_requirements and set the
load-plugins option in your Pylint config.
Updated about a month ago