curved-television-6568
10/07/2021, 6:44 AMpackage
in case of changed dependencies/set of sources and the like.)modern-wolf-36228
10/07/2021, 10:44 AMhappy-kitchen-89482
10/07/2021, 1:20 PM--loop
to rerun things on filesystem changes in an accurate and fine-grained way--loop
doesn't kill a run
process on filesystem changes, and that is hopefully not hard to changemodern-wolf-36228
10/07/2021, 1:21 PMhappy-kitchen-89482
10/07/2021, 1:23 PM./pants --changed-since-main --loop test
and it'll rerun the relevant tests as the filesystem changes. Allowing ./pants --loop run path/to/manage.py
seems like an obvious extension of that functionality, that we should support.modern-wolf-36228
10/07/2021, 1:32 PMscript
will not use its own reload system e.g. uvicorn --reload
will not be used, just uvicorn
, giving the power to pants to restart the process.
Is there a thought about the killing process already?happy-kitchen-89482
10/07/2021, 1:42 PMwitty-crayon-22786
10/07/2021, 3:55 PMpex_binary(.., interruptible=True)
… feedback welcome!--loop
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 ./pants --loop export-venv --dest $dir $targets
, and the venv would be recreated each time the inputs had changedpex-tools
entrypoint that supports creating a venv from a PEX: https://gist.github.com/stuhood/29082674e1558fbc111824a8e0ebbfb12.8.0.dev
release!--loop
with run
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 pex_binary
(and docker_image
, etc) ended up being restartable=True
rather than “interruptible”, which was ambiguous (since we will “interrupt” things when you Ctrl+C, regardless of any setting)