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

Pants

The page is getting way way to big for pypi

<@U04S45AHA>: would you accept a patch to have TaskPlanners declare the Configurations they consume, and to have that be aggregated into the symbol_table in src/python/pants/engine/exp/examples/planners.py ?

or do you have some other plan for generating the symbol_table?

i have a few other questions as well, but can save them for Wednesday or post them in some format before then?

I have no plan for the symbol table.  The main idea is just to be able to exercise the idea space - can we plan it at all.

I don't want to polish things too much so as not to discourage tearing it all down

as used, Promises seem more like Requests

Sure, it's not the promise usage you'd expect in code

am i misunderstanding the semantics there, or are they actually "requests" made for other planners to do things

It's asking for a promise, that may be contingent if required=False

ok, so a request for a promise perhaps. just a naming thing.

Why are Jars and Sources Configuration and not Products?

the Configuration scheme does seem very cool, and i think i like it a lot. seems to allow for both consume-site-parameters and produce-site-parameters

Turns out you don't need products at all to test the planner

but in the past when Benjy has said "sources are just a product", it resonated with me