curved-television-656810/07/2021, 6:44 AM
in case of changed dependencies/set of sources and the like.)
modern-wolf-3622810/07/2021, 10:44 AM
happy-kitchen-8948210/07/2021, 1:20 PM
to rerun things on filesystem changes in an accurate and fine-grained way
doesn't kill a
process on filesystem changes, and that is hopefully not hard to change
modern-wolf-3622810/07/2021, 1:21 PM
happy-kitchen-8948210/07/2021, 1:23 PM
and it'll rerun the relevant tests as the filesystem changes. Allowing
./pants --changed-since-main --loop test
seems like an obvious extension of that functionality, that we should support.
./pants --loop run path/to/manage.py
modern-wolf-3622810/07/2021, 1:32 PM
will not use its own reload system e.g.
will not be used, just
, giving the power to pants to restart the process. Is there a thought about the killing process already?
happy-kitchen-8948210/07/2021, 1:42 PM
witty-crayon-2278610/07/2021, 3:55 PM
… feedback welcome!
would still be compatible with a goal that produced a venv somewhere, if someone wants to write a goal to do that… then you could do something like
, and the venv would be recreated each time the inputs had changed
./pants --loop export-venv --dest $dir $targets
in most cases (obviously in hindsight), because if the process is long-lived it will already sit and wait for things to happen, 2) the flag on
, etc) ended up being
rather than “interruptible”, which was ambiguous (since we will “interrupt” things when you Ctrl+C, regardless of any setting)