resources
Generate a resource
target for each file in the sources
field.
Backend: pants.core
sources
Iterable[str]
A list of files and globs that belong to this target.
Paths are relative to the BUILD file's directory. You can ignore files/globs by prefixing them with !
.
Example: sources=['example.ext', 'test_*.ext', '!test_ignore.ext']
.
dependencies
Iterable[str] | None
None
Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].
This augments any dependencies inferred by Pants, such as by analyzing your imports. Use ./pants dependencies
or ./pants peek
on this target to get the final result.
See https://www.pantsbuild.org/v2.10/docs/targets#target-addresses and https://www.pantsbuild.org/v2.10/docs/targets#target-generation for more about how addresses are formed, including for generated targets. You can also run ./pants list ::
to find all addresses in your project, or ./pants list dir:
to find all addresses defined in that directory.
If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. :tgt
instead of helloworld/subdir:tgt
. For generated first-party addresses, use ./
for the file path, e.g. ./main.py:tgt
; for all other generated targets, use :tgt#generated_name
.
You may exclude dependencies by prefixing with !
, e.g. ['!helloworld/subdir:lib', '!./sibling.txt']
. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.
description
str | None
None
A human-readable description of the target.
Use ./pants list --documented ::
to see all targets with descriptions.
overrides
Dict[Union[str, Tuple[str, ...]], Dict[str, Any]] | None
None
Override the field values for generated resource
targets.
Expects a dictionary of relative file paths and globs to a dictionary for the overrides. You may either use a string for a single path / glob, or a string tuple for multiple paths / globs. Each override is a dictionary of field names to the overridden value.
For example:
overrides={
"foo.json": {"description": "our customer model"]},
"bar.json": {"description": "our product model"]},
("foo.json", "bar.json"): {"tags": ["overridden"]},
}
File paths and globs are relative to the BUILD file's directory. Every overridden file is validated to belong to this target's sources
field.
If you'd like to override a field's value for every resource
target generated by this target, change the field directly on this target rather than using the overrides
field.
You can specify the same file name in multiple keys, so long as you don't override the same field more than one time for the file.
tags
Iterable[str] | None
None
Arbitrary strings to describe a target.
For example, you may tag some test targets with 'integration_test' so that you could run ./pants --tag='integration_test' test ::
to only run on targets with that tag.