@hundreds-father-404: fwiw, an incantation that replaces the

--type

arg on `dependencies`:

./pants dependencies --transitive :: | xargs ./pants filter --target-type=python_requirement_library | xargs ./pants peek | jq '.[]["requirements"][]'

definitely more consistent. I support that until we have a more generic "query"

it also seem like

peek

could gain the ability to render a single field, to avoid the need for

jq

? a bit complicated here though because it’s a single entry list in this case

Yeah I think

./pants peek --field=requirements

. Unclear if you warn, error, or ignore when the target doesn't have that? What if it instead filtered out all targets w/o the field, so

./pants peek --field=requirements ::

is like

./pants filter --target-type=python_requirement_library | xargs ./pants peek --field-requirements

hm, i don’t think the filtering is the issue i see: more that

requirements

is a string list: if you just dump it, your output is a list of string lists

oh, hm, yeah, I don't think

./pants peek --flatten

or

./pants peek --merge

makes sense because some fields aren't mergable, like the

setup_py()

field of

python_distribution

that's actually why I thought that just leaving it as json was the easiest move... you're outputting arbitrary data structures, so you don't know how you want to handle things like "flattening" in the general case

yep. good call.

As long as we document a couple cool/useful queries for users, both in the docsite and probably

./pants help

, I think this is a great idea to fix. Don't make them figure out this incantation for req strings

--type

is so broken I don't think it's worth salvaging

we didn’t, no.