Skip to main content
Version: 2.8 (deprecated)

dependencies

pants dependencies [args]

List the dependencies of the input files/targets.

Backend: ``

Config section: [dependencies]

Basic options​

closed​

--[no-]dependencies-closed
PANTS_DEPENDENCIES_CLOSED
pants.toml
[dependencies]
closed = <bool>
default: False

Include the input targets in the output, along with the dependencies.

output_file​

--dependencies-output-file=<path>
PANTS_DEPENDENCIES_OUTPUT_FILE
pants.toml
[dependencies]
output_file = <path>
default: None

Output the goal's stdout to this file. If unspecified, outputs to stdout.

sep​

--dependencies-sep=<separator>
PANTS_DEPENDENCIES_SEP
pants.toml
[dependencies]
sep = <separator>
default: \n

String to use to separate lines in line-oriented output.

transitive​

--[no-]dependencies-transitive
PANTS_DEPENDENCIES_TRANSITIVE
pants.toml
[dependencies]
transitive = <bool>
default: False

List all transitive dependencies. If unspecified, list direct dependencies only.

Advanced options​

None

Deprecated options​

type​

--dependencies-type=<DependencyType>
PANTS_DEPENDENCIES_TYPE
pants.toml
[dependencies]
type = <DependencyType>
one of: source, 3rdparty, source-and-3rdparty
default: source
Deprecated, will be removed in version: 2.9.0.dev0.
This option is misleading and not very useful. In the future there will be a more robust way of querying and filtering dependencies.<br />Meanwhile you can get the list of requirement strings for a set of targets using something like<br /><br />./pants dependencies :: <br />| xargs ./pants filter --target-type=python_requirement <br />| xargs ./pants peek | jq -r '.[]["requirements"][]'<br />

Which types of dependencies to list, where source means source code dependencies and 3rdparty means third-party requirement strings.

None