Documentation to use pipx-managed pipx as an alternative installation option.

[huxuan]

How would this feature be useful?

There is a warning about "not recommended to install pipx via pipx" in the documentation, but it seems to be outdated, especially for the referenced pipx-in-pipx project. Moreover, more and more issues are caused by using an old version of pipx especially on Ubuntu 22.04. For me, I use pipx-managed pipx almost everywhere, MacOS laptop, Linux Server and Windows Workstation, and it works quite well. Maybe it is time to drop the warning.

Describe the solution you'd like

Remove the warning from documentation and add pipx-managed pipx as an alternative installation option.

Describe alternatives you've considered

Mark the pipx-managed pipx as an experimental installation option currently.

[Gitznik]

I have never tried using pipx that way, but if no one remembers why and what issues there were around it, IMO we should remove the warning.

[huxuan]

I know there was an issue about the DEFAULT_PYTHON and it was fixed by #1340.

[epx5k]

Seems reasonable to Remove the warning from documentation and add pipx-managed pipx as an alternative installation option.

…

On Jun 11, 2024, at 8:06 AM, Xuan (Sean) Hu ***@***.***> wrote: Remove the warning from documentation and add pipx-managed pipx as an alternative installation option.

[j0057]

It's pretty easy to do this without pipx-in-pipx:

python -m venv /tmp/bootstrap
/tmp/bootstrap/pip install pipx
/tmp/bootstrap/pipx install pipx
rm -rf /tmp/bootstrap