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 was gonna move it to the front of the PATH for sure

i thought that later after i opened the RB

i dont know about sanitizing the whole path

<@U066LC126>: created an RB that tries to do excludes ‘the maven way’  (mimicing &lt;scope&gt;provided&lt;/scope&gt;)  That is you specify on the jar() decl that you don’t want to deploy with this jar.  See <https://rbcommons.com/s/twitter/r/2897/>

that could make things more reproducible, but sanitizing away your PATH could be really limiting

i think it could be too limiting for people who might need it sometimes

I think in general the cycle guess is correct. The execution_graph while block on line 282 never completes. The 6gb+ data structure in the heap is the finished_queue being infinitely packed with canceled jobs.

<@U053H6LQS>: I’ll check it out later this afternoon

<@U09KGJ23Y>: k... just getting the ordering correct now would help

can think about path blacklist or something later

<@U04S45AHA>: <@U06A03HV1> added unit test, fixed PATH order and handling of empty string in env PATH case under <https://rbcommons.com/s/twitter/r/2883/>

A heads-up that I'm working on a change to move build graph-related stuff out of `src/python/pants/base` and into `src/python/pants/build_graph`. This should make it a bit easier to reason about that code in isolation. Any objections?

There may also end up being a `src/python/pants/invalidation`.

base has become a crazy catch-all, and it imposes weird deps that ripple out everywhere.

<@U051221NF>: what kinds of stuff?  not things like ‘target’ and ‘payload’ I hope.

I’m just looking through all the imports in our plugins...

Imports are easy to mechanically refactor

not sure about Target and Payload yet, but they seem like a lot more of a hassle.

Right now I'm looking at BuildFileParser, BuildConfiguration, Addressable etc etc

I really really don’t like having all my plugins break to test a minor change to pants.

Well, it's easy to maintain the old names through a deprecation cycle.

<@U051221NF>: <@U054MQUPL> and <@U07J10LLW> will be interested... they're currently working on the daemon and touching the build graph quite a bit

... although priority wise, i wonder whether we want to slow down there and focus on the engine for a while.

is the goal of that refactor to help with the engine somehow?

No, it's to start reasoning about possible alternate, more-efficiently-parseable, BUILD file formats.

After looking at CPU profiles for a couple of days, I'm increasingly convinced that it's time for BUILD.json...