I would like to then change our docs to recommend trying this out preferably to other ways of installing Pants.

I'm upgrading us to the latest RC this. I'll remove the pants script at the repo root and force my devs to use this instead. 👍

I already wrote that script fwiw a few weeks ago: https://github.com/pantsbuild/scie-pants/pull/48

Will overwrite mine with that one, and then maybe tweak a little

Should we augment the pants script to use one-or-the-other so people can switch?

That would mean: curl the augmented Pants script, which curls the get-pants (or pantsup) script, which curls scie-pants.

🏋️‍♂️

It's the difference between

pants

and

./pants

Putting this in

./pants

makes it easy to try, way to wean, and easy to switch

Easy to try how?

pants

vs

./pants

is pretty subtle; so you leave the cliff of learning that for later anyhow. In effect the only thing you buy is ... I actually have no clue.

We pretty regularly have ./pants throughout all the docs for code samples. Once you make the change, you'll want to grep and update all references (ripgrep + the fd replacement for find is great combo)

@enough-analyst-54434 ./pants is at the root of every pants repo for every user. Slack is checked by maybe a couple handfuls. Having the launcher script download it for you and nudge you towards the future is better than pulling the rug. Speaking of, there's 0 discussion on how to deprecate ./pants anyways.

Josh we agree on goals but not details. If you're an existing user you need to update your pants script. What triggered that? If you're a new user you just use the new thing Benjy is documenting.

Updating

./pants

is probably a good idea because of all the muscle memory of typing

./pants

. But we can't get away from socializing the need to update

./pants

...

Can someone explain what it means for

./pants

to wean you off

./pants

? Afaict, a new pants script either has to look for a new config option to say I want to use the new Pants launcher or it just defaults to the new launcher. If that's right, then the new Pants script does not wean you off itself, it just gets usage time of the new launcher. So you're getting vet time of the launcher; not weaning users. Users will still face the

./pants

->

pants

cliff.

Still makes zero sense to me. I'll bow out.

I guess it's to say "stop using me, use

pants

instead, I will stop working soon"

So there will be a nag message added.

Yeah, that is what I was imagining @bitter-ability-32190 was suggesting?

That and we can also install the script in

bin

for them. Eventually shelling out to it by default. Helps users with less steps and helps make it a gradual transition