has anybody noticed isort shuffles stuff around based on what targets you call `lint`/

fmt

on? We've had some issues where our pre-commit hook that uses

--changed-since=HEAD lint

isort will complain about making changes, but then when you manually do

fmt ::

nothing will change

yes, the pants sandboxing can interfere with `isort`’s inference of what’s 1st party and what’s 3rd party (i.e. if the sandbox omits one of your modules,

isort

will think it’s a 3rdparty-dep)

I suspect this is due to https://github.com/pantsbuild/pants/issues/15069