Hi all, have some questions on the list of targets that are generated by the pants build. I have a BUILD file for my pytests as such:

python_sources()

python_tests(
    name="tests0",
    sources=["test_a.py"],
)

python_tests(
    name="tests1",
    sources=["test_b.py"],
)

python_tests(
    name="tests2",
    sources=["test_c.py"],
)

and

./pants list

returns the following:

repo/test:tests0
repo/test:tests1
repo/test:tests2
repo/test/test_a.py:test0
repo/test/test_b.py:test1
repo/test/test_c.py:test2

python_tests

is a “target generator”, which generates a target per file: the generator itself has a name, and each generated

python_test

target does too. see https://www.pantsbuild.org/docs/targets#target-generation

Oh interesting, I assumed I needed to create a separate target to run things in parallel

no need.

This was super helpful. Thanks @witty-crayon-22786

sure thing. yea, if

tailor

doesn’t get you a good experience out of the box, an issue would be appreciated… our goal is that folks mostly don’t need to hand-edit

BUILD

files, except to add metadata

@witty-crayon-22786 the only thing I had to add was a dependency for datasets that were used in my pytest.

tailor

didn’t seem to pick that up.

ah, yea: “asset inference” (for

file

and

resource

targets) is disabled by default, but you can enable it: https://www.pantsbuild.org/docs/reference-python-infer#assets