Hi, is there a way to get pants to output 3rd party requirements for a target in a

requirements.txt

format? It looks like

./pants dependencies

used to do this with

--type=3rdparty

(see ) but that option seems to have disappeared.

Something like that, yeah... The old way of doing this was perhaps more convenient for this specific use-case, but very ad-hoc

Thanks - I don't mind wrapping the above in a script or something, but I'd have preferred to avoid doing that if Pants supported it directly.

There are various examples here that we could add to: https://www.pantsbuild.org/docs/project-introspection

Ah that must be where that youtube video came from! (A colleague sent me the link - presumably he got it from that page.)

thanks, Alex, this is great. I was exploring this myself in https://pantsbuild.slack.com/archives/C046T6T9U/p1671482123490549 a couple weeks ago.

for posterity, I ended up with

pants dependencies --dependencies-transitive <target> | tr '\n' '\0' | xargs -0 pants peek --filter-target-type=python_requirement | jq -r '.[]["requirements"][]' | sort -u

where •

tr '\n' '\0'

and

xargs -0

account for target names that contain characters that

xargs

would normally split on (eg spaces/tabs) •

sort -u

accounts for cases where

xargs

invokes

pants peek

more than once, and combines the output. (This happens in cases where

pants dependencies

outputs many targets, eg if you pass in

::

.)