pipx-in-pipx 1.0.1

Which Python?

By default, pipx uses its own Python for each environment that it creates. Normally, this would be the system Python, whatever it was when you installed pipx. However, when your are using a pipx-in-pipx-installed pipx, the default Python that pipx uses for each environment it creates is instead whatever Python you used to “install” pipx-in-pipx.

This has two notable side effects:

1. If you uninstall your pipx-managed pipx, then all of the tools that you installed using that pipx will stop working because their Pythons suddenly point to nothing.

2. If you want to change the Python used by all of your pipx-managed tools, you only need to reinstall one of them (pipx) rather than reinstalling all of them.

Uninstalling

pipx has a handy feature to uninstall all pipx-managed tools. Because you have now made pipx manage itself, running pipx uninstall-all will also uninstall pipx.

This is not a bug, but a feature. By installing pipx using pipx-in-pipx, you have expressed an intent that you want pipx to manage itself. If that’s not what you want, this is not the tool for you.

If you at any point uninstall your pipx-managed pipx, you can simply pip install pipx-in-pipx again to rebuild it.