loud-laptop-17949
10/26/2022, 6:23 PMbitter-ability-32190
10/26/2022, 6:24 PMhundreds-father-404
10/26/2022, 6:27 PMloud-laptop-17949
10/26/2022, 6:28 PMwitty-crayon-22786
10/26/2022, 6:28 PMtailor
to create those targets? it should automatically create the python_test_utils
if you need themwitty-crayon-22786
10/26/2022, 6:28 PMloud-laptop-17949
10/26/2022, 6:29 PMpython_sources
in a bunch of places where it should be python_test_utils
. I tink most of those were from before python_test_utils
existed.loud-laptop-17949
10/26/2022, 6:30 PMeager-dress-66405
10/27/2022, 6:11 AMpython_sources
targets for most of these. It correctly makes a python_test_utils
for conftest.py
etc, but most of the files we're talking about here are just regular python modules that happen to live under a tests
directory (the convention in our codebase) and are only imported from actual tests.eager-dress-66405
10/27/2022, 6:14 AMpython_sources
from depending on python_test_utils
, but I don't actually see that documented on https://www.pantsbuild.org/docs/reference-python_test_utils. They also show as python_sources
when using ./pants peek
or --filter-target-type
. It would be nice is there was some way to differentiate these when querying pants.