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

Pants

which, misleadingly, is _not_ full of (contrib) plugins... just backends

those are loaded only in the pantsbuild/pants repo by virtue of being adding to the pantsbuild/pants pants.ini file (rather than to the default for the `backends` option)

Unrelated: Ugh python inheritance hierarchies :disappointed:

So, talk to me about `Address` vs `BuildFileAddress`

wait! you just said you wanted inheritance! :wink:

I need a `BuildFileAddress` because that type indicates that it’s been parsed out of build files?

BuildFileAddress is a subtype of Address that holds a reference to the BUILD file it was parsed from

But what I actually want is an `Address`; I’m only asking for a `BuildFileAddress` because I care that it was parsed out?

i think BuildFileAddress used to be necessary to satisfy some interface or another... possibly the go BUILD gen tasks use it...?

we deprecated away the old build file parsing code though... so it might be possible to nuke entirely. unsure

Ok, I have made my slightly absurd edits :smile:

OH GOD PYTEST WHY DO YOU THINK EVERYTHING IN THE WORLD IS A TEST?

<https://docs.pytest.org/en/latest/example/pythoncollection.html#changing-naming-conventions> - but ingraining the std patterns as things to avoid in non-test naming was always a workable strategy for me.

`s/def test_coordinator/def coordinator_of_tests/`

<https://github.com/pantsbuild/pants/issues/6657>

<@U06A03HV1> Addressed all comments on the top PR, will back-port to the appropriate ones tomorrow :slightly_smiling_face:

<@U0AALHEDR>: two comments: 1) i think the lost cursor thing might be out of scope if i understand correctly. 2) see my ping from Daniel's review... an independent entrypoint next to `Scheduler.product_request` might be in order for the `@console_rule` usecase

and it would be useful for you, because that would be your `render_the_ux=True` codepath

...ok, i see what you mean about the cursor. that would be good to fix there, yea

i don’t have a quick idea how exactly yet. so might as well do it separately

i’d assume adding the `render_v2_engine_ui` option to `ExecutionOptions` would be incorrect? <https://github.com/pantsbuild/pants/pull/6647/files#diff-75fd6e699e8dc92731600eccad4e1520R79>

<@U0AALHEDR>: an actual pants option would be fine, yea. but it must still be conditional in various codepaths

_only_ `@console_rules` should trigger rendering. and then, only if "global option enabled"