Thanks to @happy-kitchen-89482’s https://github.com/pantsbuild/pants/pull/15689 I was inspired to write an in-repo plugin to do the same for

./pants run path/to/file.py

(I plan on upstreaming it, but it will take careful planning). Aside from a few quirks the new model introduces that needed smoothing, this has eliminated all need to migrate most of our 200

py_binary

rules. That's at least month of my time saved, and a year's worth of my org's time. After removing those rules, running my Bazel tree pruning 14 times (so we trimmed leaf nodes 14 times until all thats left is used for docker images), we now have removed just shy of 5000 lines of Bazel BUILD.

You are welcome 😽

And of course, shoutout to

tailor

for adding all those python sources to my Pants build files 😛

That was indeed an inspired idea. So glad Alexey suggested it.

I love us not being scared to advocate for bazel tools as well, where they fit

Absolutely. Use the best tool for the job. This is what open source is great for. That Bazel's tools are in this case helping you to ditch Bazel, well, 😇 ...