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

Pants

right... but that's already the case with `target.id`s

ack - not talking about those, and those have never been used for user-facing

the fact that this will "usually" be user facing ("where is my bundle?") might mean directory structures are the way to go.

Agreed that mirroring at least some of the structure likely makes sense

But also, I'm still a strong proponent of scope namespacing 1st as much more important

in the intellij case, <@U071M9KNE> knows which targets to look for, so it's not a hardship that there isn't a single directory to list to get all outputs

at the same time, we're headed in the opposite direction in `.pants.d`... targets have a `results_dir`, not tasks

or, it's the opposite direction in that the default is to constrain directory usage

PSA: <https://rbcommons.com/s/twitter/r/3071/> changes how we handle the version-request flags, `-v`, `-V`, `--version` and `--pants-version`. The first three now no longer take an optional argument, and  display the current version. `--pants-version` now requires an argument, and pants verifies that it's running against that version. This also documents the pants_version key in pants.ini, which is used by scripts etc.

TL;DR If you're calling `--pants-version` with no arguments in your repo, please change that to `--version` now (you don't need to wait for a pants upgrade).

<@U051221NF>: I don’t fully understand why we used to take an optional argument in the first place.

We wanted `--pants-version` to serve two unrelated purposes:

- With no arg: show the version and exit.

- With an arg: don't choke on this in pants.ini, because scripts outside of pants use it.

But that first purpose is unnecessary, we already have 3 other flags for that.

so if someone has a pants.ini file or a script that passes a value to any of these they will blow up after this change?

yes. but in theory only the pants repo itself was doing this.

To be clear - no one sets -v --version in pants.ini today

yeah, I agree… don’t get me wrong I’m all for getting rid of this hack.

This is one of those 1% deprecation subjects

Can we add something to the summary that indicates its a backwards incompatible change or something?