Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

But list not being optimized makes complete sense

i'm going to ask <@U07A47275> to look deeper into whether we (twitter, or pantsbuild even) should consider switching by default

SGTM, basically if it can be shown that its generally useful or even useful just for specific cases we support, I'd like to get a CI job setup for pypy

```-PY=${PY:-$(which python2.7)}
+PY=${PY:-$(which pypy)}```

Question: Is there a way from the command line to express the set of targets that all end in ‘:test’?   like:
```
./pants test foo::test
```

would recommend doing tags instead, honestly

If its not for an end user, or even if it is, a pipeline with xargs and works well enough for lots of things

Well, it is for an end user.  They are used to running their tests with `./pants test foo::`  but now they want to add some integration tests that don’t run on developer laptops. I wanted to give them a way to run just the unit test targets.

I'm actually surprised coming from mvn you did not already have Stu's suggestion

In my maven go rounds we always hand set up an src/test/IT/

(downside of tags being that you have to remember to pass a flag, as opposed to running under a directory)

./pants test multipass:: --tag=-integration-tests

<@U06A03HV1>: re: pypy, I’m mildly concerned about relying on it just due to vendor/support related things. maybe we could just analyze what makes pypy faster in this particular case and then either implement that optimization ourselves or bust out a c-lib optimization.

<@U054MQUPL>:  that sounds painful :smiley: