(On 2.13.0rc0) Is it possible `paths` is broken? I...
# development
f
(On 2.13.0rc0) Is it possible
paths
is broken? It seems to be outputting
[]
no matter what, even for trivial dep paths like direct dependencies
Copy code
sh-5.1$ ./pants dependees //tests/sorted_components.py:../testlib
//:testlib
//tests/local/components.py:../../testlib
sh-5.1$ ./pants paths --paths-from=//tests/sorted_components.py:../testlib  --paths-to=//tests/local/components.py:../../testlib
[]sh-5.1$
👀 1
1
h
hmm I reproduce. Thanks! On it
🙇🏻 1
Wait no I don't reproduce. I forgot that
[]
means "no path". Try flipping the
from
and
to
-- do you see something?
btw, you can simply do
./pants paths --from=... --to=...
, i.e. leave off the
paths-
w
dependees
is the inverse of
dependencies
so you’d need to swap the order of from and to there
f
ah
dammit that was too easy
w
s’all good…
dependees
is a pretty rare usage…
dependents
is more common. but we’ve used it for so long that it’s stuck (so far)