Hi @cs01! Thank you for doing this. This content is great, but I'd prefer it be under "guides" instead of "tutorials". The reason being is that tutorials should be focused on accomplishing a single task with the minimal amount of tools and information. In fact, this particular tutorial has been on my list to clean up for a while. "Guides", on the other hand, are great for things that explore specific use cases. How would you feel about moving this to a guide and possibly linking to it from the tutorial?

Thanks for the quick reply!

How would you feel about moving this to a guide and possibly linking to it from the tutorial?

Sure, not a problem.

Which part of the guide do you think it belongs in? And what type of content should I leave in the tutorial? The same section that I just added but with just a link to the guide?

A new guide, all for itself! Something like "Installing stand-alone command line tools" would work.

And what type of content should I leave in the tutorial?

Maybe just a note or a link at the bottom that says something like "If you're looking to install stand-alone command line tools, consider using pipx".

Awesome, thank you! Will add a new commit tonight or in the next few days when I have the time.

Replaced tutorial with new guide "Installing stand alone command line tools" and also added a link in the installation tutorial.

Tangent: only reading the comments without reading the PR itself, I was confused by the fact that https://pypi.org/project/pipx/ is not the pipx being referred to here. So while I can understand the desire to use the name pipx by analogy with npx, I think it will be incredibly confusing for end users when the naive bootstrapping approach of running pip install --user pipx and managing pipx using pip rather than itself doesn't actually work. (Before reading your guide I assumed I'd be able to just replace pipsi with pipx in my current bootstrapping instructions, but that isn't the case)

The simplest resolution might be to open on issue on https://github.com/khalti/pipx and ask the Khalti folks if they'd be willing to relinquish the pipx name on PyPI to you - given the only change they've made since August 2017 is to add a note pointing out that the project isn't actually maintained, they may be willing to help you out.

I don't think that concern should block merging the guide though - I'll just note in the draft guide where I think a bit more clarification would be helpful.

Actually, that would be ideal. @cs01 Do you mind holding off on this until we hear back from the pipx folks? If you would like, I can reach out to them on your behalf.

Actually, that would be ideal. @cs01 Do you mind holding off on this until we hear back from the pipx folks? If you would like, I can reach out to them on your behalf.

Sounds good. I was going to suggest the same thing to avoid churn in the docs. Nick's request was agreed to (khalti/pipx#2), so now I am waiting on @ludbek to grant me access.

@ncoghlan @cs01 Its done. Good luck with the new project.

@ludbek Thank you!

@ncoghlan thanks for helping to get the pipx name transferred over to me 😄.

@ncoghlan @theacodes I've updated pipx on PyPI and these docs, so it's ready for another review 😄.

@theacodes Since this is a whole new guide, l figure it's worthwhile leaving pushing the big green button to you so that it gets two pre-merge reviews :)

Thank you, @cs01 for writing and @ncoghlan for reviewing. :)