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

Pants

I leave that up to you...I  use alias because that is what we have them install in register.py

If they want to get extra arbitrary target to a task I presume they must have at least created a custom target

Wait...target_alias is the string rep of a Target, 

But it is the only other place we would have that repr

`target(name='blah', ...)` or `alias(name='blah', ..)` is what we tell people are "target aliases" internally

If you have a ScalaLibrary foo, foo.target_alias == 'scala_library'

So that was my reasoning, for the most part

Not a sticking point for me, but what I have personally been doing

I changed most of the isinstance checks to string comparisons

To make 3rdparty plugin consumption a little more sane to config in ini files

<@U06A03HV1> Do bazel and buck (am I allowed to mention their names, or is it like Voldemort ?) have a similar powered by page? I can't find one.

I gotta run and get my son, so up to you, my shipit stands. Thanks for following up, Stu. I threatened data services team with it just today :)

<@U051221NF> : since we're going to have one final rc for the scalafmt stuff, how risky do you think it would be to get the default sources change in as well? seems like it goes well as a package with the default name change.

well all of our targets have sources specified right?

in theory. also, off by default. so probably minimally risky.

<@U16S4PPTQ> : no worries mentioning them... just don't know the answer. they didn't when we did our research last year

Seems like you guys are where it's at when it comes to adoption.

pants definitely has the most diverse community, hands down

bazel is largely developed on by Google and buck is the same re: Facebook

<@U06A03HV1> I don't have anything holding back the pants 1.2 release.

sounds like <https://rbcommons.com/s/twitter/r/4329/> will likely be the final rc then.