Closed mgorfer closed 1 year ago
@mgorfer This is a bug in isort itself. See https://github.com/PyCQA/isort/issues/1989
Unfortunately, they have not released it yet (see https://github.com/PyCQA/isort/blob/main/CHANGELOG.md).
The workaround is to specify the config file manually.
Duplicate of https://github.com/microsoft/vscode-isort/issues/53
Using the VSCcode isort extension, the custom headings which I defined in my
isort.cfg
in the root of my repository are ignored. Theknown_first_party
modules from that file are recognized though and everything is moved to the correct section (without headings). Usingisort
in the terminal, the correct headings as defined in myisort.cfg
are applied.When specifying this file in the
isort.args
using["--settings-file", "xyz/.isort.cfg"]
in my VSCodesettings.json
, the headings are applied.My
isort.cfg
: