The Python import sorter tool (https://timothycrosley.github.io/isort/).
Don't use isort when running `./pants fmt` and `./pants lint`.
Arguments to pass directly to isort, e.g. `--isort-args="--case-sensitive --trailing-comma"`.
Requirement string for the tool.
--isort-extra-requirements="['<str>', '<str>', ...]"
[ "setuptools" ]
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.
--isort-interpreter-constraints="['<str>', '<str>', ...]"
[ "CPython>=3.6" ]
Python interpreter constraints for this tool.
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 config file understood by isort (https://pycqa.github.io/isort/docs/configuration/config_files/).
Setting this option will disable
[isort].config_discovery. Use this option if the config is located in a non-standard location.
If using isort 5+ and you specify only 1 config file, Pants will configure isort's argv to point to your config file.
If true, Pants will include any relevant config files during runs (`.isort.cfg`, `pyproject.toml`, `setup.cfg`, `tox.ini` and `.editorconfig`).
[isort].config instead if your config is in a non-standard location.
Updated 4 days ago