Hey all I m seeing a strange issue in the Python monorepo I

Question

Hey all I m seeing a strange issue in the Python monorepo I m working in We have several formatters setup autoflake black and isort and I ve run them over the whole repository with ` pants fmt ` After this ` pants lint ` shows the linters are satisfied with the work they ve done However if I then run ` pants lint subdirectory ` some of the linters complain that they would make changes `isort` in particular Any idea what s going on here ` pants tailor` succeeds without issue so the BUILD files look to be in order m seeing a strange issue in the Python monorepo I m working in If I run

bitter-ability-32190 · Answer

I think you re seeing an `isort` quirk See <https www pantsbuild org docs python linters and formatters isort possible issues with its import classifier algorithm>

bitter-ability-32190 · Answer

TL DR `isort` as I understand it pokes around the directories to try and deduce firstparty code If someone of those dirs aren t in the bucket we re using for formatting isort doesn t recognize the import as firstparty

flaky-artist-57016 · Answer

Ahh that makes sense Because the changes `isort` tries to make in those subdirectories effectively reverts some of the changes it makes when running over the whole repo

bitter-ability-32190 · Answer

<https github com pantsbuild pants issues 15069> is relevant here

happy-kitchen-89482 · Answer

Yeah this is an unfortunate feature of isort I think the most robust workaround is to set the firstparty package explicitly in isort config

flaky-artist-57016 · Answer

Thanks I got it sorted out after some reading and tinkering For anybody else that runs into this you ll need to list your first party imports in `known first party` in your isort config Here is an example ```known first party = module one module two module three other module```