Huh. So turns out with our `pants_run` integration...
# development
h
Huh. So turns out with our
pants_run
integration tests, we're not by default putting
__pycache__
/
.pyc
files in
pants_ignore
. Which means our file watcher is invalidating on wayyy more than we want. I suspect it explains why our ITs are so slow
1
Does it seem fine to put
__pycache__
in our default
pants_ignore
? Note that usually users have it already covered in their
.gitignore
tho Alternatively, I can improve our
run_pants
integration test to auto-set it
Which means our file watcher is invalidating on wayyy more than we want.
Which is because we run Pants via
python -m pants
, with all our
src/python/pants
files present, which causes those files to get compiled
w
it shouldn’t matter, since those files are written before the process starts up
… oh. but not for plugin code.
those would likely be reasonable defaults in
pants_ignore
.
👍 1
h
just as
pants_ignore
default, not special-cased to be hardcoded no matter what, right?
w
yea
(we have other stuff in there i think?)