filter

Filter the input targets based on various criteria.

Most of the filtering options below are comma-separated lists of filtering criteria, with an implied logical OR between them, so that a target passes the filter if it matches any of the criteria in the list. A '-' prefix inverts the sense of the entire comma-separated list, so that a target passes the filter only if it matches none of the criteria in the list.

Each of the filtering options may be specified multiple times, with an implied logical AND between them.

Backend: pants.backend.project_info
Config section: [filter]

Basic options

`output_file`

--filter-output-file=<path>

PANTS_FILTER_OUTPUT_FILE

default: None

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

`sep`

--filter-sep=<separator>

PANTS_FILTER_SEP

default: \n

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

`target_type`

--filter-target-type="[[+-]type1,type2,..., [+-]type1,type2,..., ...]"

PANTS_FILTER_TARGET_TYPE

default: []

Filter on these target types, e.g. resources or python_sources.

`granularity`

--filter-granularity=<TargetGranularity>

PANTS_FILTER_GRANULARITY

one of: all, file, BUILD
default: all

Filter to rendering only targets declared in BUILD files, only file-level targets, or all targets.

`address_regex`

--filter-address-regex="[[+-]regex1,regex2,..., [+-]regex1,regex2,..., ...]"

PANTS_FILTER_ADDRESS_REGEX

default: []

Filter on target addresses matching these regexes.

`tag_regex`

--filter-tag-regex="[[+-]regex1,regex2,..., [+-]regex1,regex2,..., ...]"

PANTS_FILTER_TAG_REGEX

default: []

Filter on targets with tags matching these regexes.

Advanced options

None

Deprecated options

None

Updated about 1 month ago