[Question]: Why not just using pip?

[deeplook]

I've managed to install fabric using the new method with pipx and now I wonder what the advantages are over pip? I see pipx imposes its own environment management on the user which only adds to the number of tools people need to use if they use one of the way more popular ones like virtualenv or conda. On my macOS system it added another new location for virtual environments, another Python and a lot of more stuff when running brew install pipx.

I've read that pipx might support symbolic links better than pip only. But then one could also have a single fabric command installed that knows about a few subcommands like ytetc. It's only a tiny bit more inconvenient, but adds a lot of consistency to the CLI.

I know the installation of fabric was less convenient before using pipx, but it seems still a long way to the simplicity of a single pip install command, and the corresponding listing on pypi.org. Questions by other users like https://github.com/danielmiessler/fabric/issues/267 seem to support this. And you would not need to clone or download the sources from github to start with.

Therefore I'd kindly ask to reconsider the installation mechanism with the goal of providing a simple pip install command and let the user pick his own virtual environment manager.