I'm curious how many of y'all develop and then plug into pants vs. using pants as a part of your dev process; do you write your code and then instrument with pants post-dev/pre-CI, or do you instrument pants from the beginning and use it during your development process?

I tend to have a

pants --loop test …

session going while I develop, so any relevant test cases I work on gets run each time I save.

All code in our Pants repository only gets tested/linted/... through pants. Most of my developers use a cli-alias to run all checks we care about, all local code execution is with

pants run ...

, etc. We also build our containers through pants, though that almost exclusively happens on CI. Very few engage with it beyond that though. It's just another way of spelling

pdm

or

cargo

or

bazel

for the others, and I'm perfectly happy that they feel that way, while Pants lets me focus on more important work than manually maintaining all our workflows.

thanks to you both! very helpful info

Oh! One thing more that I thought about now. One of my colleagues loves how easy it is to debug code and unit tests using

--debug-adapter

, and even wrote an internal guide for other developers on how it works in Pants.

that's one of my big curiosities! I will look into that option for sure.. I imagine the guide is IP but if it's available to share I'd love to take a look

I think maybe "guide" set too big expectations! We internally call them recipes; so it should be <1 page and easy to reproduce. So first one is the debugging recipe, second one is a repl recipe. Rest contain a bit too much detail about our work.

ah got it! very cool. thanks again!