Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

I am running the fmt goal and observing a discrepancy that fmt is not picking up the target when run on all targets, but works when a precise file is given.

% _`./pants`_ _`fmt`_ _`::`_
...
✓ black made no changes.
✓ docformatter made no changes.
✓ isort made no changes.  &lt;--- HERE
% _`./pants`_ _`fmt`_ _`projects/appsflyer/appsflyer/apps/appsflyer/views.py`_
...
✓ black made no changes.
✓ docformatter made no changes.
+ isort made changes.   &lt;--- HERE
% _`./pants`_ _`list`_ _`::`_
...
projects/appsflyer/appsflyer/apps/appsflyer/views.py &lt;-- THE TARGET IS PRESENT
...

So this is kinda an isort blight exposed through pants.
See <https://github.com/pantsbuild/pants/issues/15069|https://github.com/pantsbuild/pants/issues/15069>

TL;DR isort looks around to deduce first party sources. In the first case it's deducing from the other files. If you only give it one it has nothing to go on :smiling_face_with_tear:
Easiest fix is to configure isort

Indeed, a very unfortunate issue. Also mentioned here <https://www.pantsbuild.org/docs/python-linters-and-formatters#isort-possible-issues-with-its-import-classifier-algorithm>

Yeah, I referred this in the example repo.