Bumping this question around dep inference on deletion. Do we have a way of including former dependees in the scope of affected files with

--changed-dependees=transitive

?

Clearly you can script the requirement above outside of Pants. Maybe not bad for CI. Less good for devs.

wt=$(mktemp -d)
git worktree add -f $wt $changed_since_ref > /dev/null
cd $wt
./pants dependees --transitive ${deleted_files[@]}
cd -
git worktree remove $wt > /dev/null

is the best i can come up with off the top of my head

okay we've got some work to get there since we're not inferring 3rd party deps (we're about to add RPM inference of python packages to enable this), but that does look like a decent ticket for 95% of my cases

I think combined with

unmatched_build_file_globs = error

it might cover 99% but I can come up with an edge case: removing a conftest.py in a test folder that contains other sources that match the

sources

globs in the

python_test_utils

target (like

blah_tests.pyi

or something custom). Because of the other sources,

unmatched_build_file_globs

won't trigger, and because nothing explicitly imports conftest,

unowned_dependency_behavior

won't catch that. Otherwise I think you're right that those two options do it. But this seems to be a consequence of the kinda magical behavior of

conftests