@simon voted yes, but really it's "I _sometimes_ use pipx” - a lot of the time I'll still just regular-pip install into an appropriate virtualenv, because lazy or because reasons

@simon I used to! Now I use nix.

@simon I prefer using the OS package manager and use pipx if the package manager doesn’t have what I need.

@simon

Yes, as non-admin user on linux after python3.11, installing to ~/.local/bin

@simon Huh, discovered it just now. Thanks

@simon brew is preferred, but pipx is great for things not big enough to be there.

I do prefer local installs for project-specific tools (like pytest, where I just have many copies of it on my computer). But for general purposes utilities that happen to be written in Python, pipx is perfect.

@simon If it is in python and has a CLI interface, it should be installed with pipx unless you enjoy trouble shooting incompatible libraries. If the tool needs to be able to run `import yourcode`, such as mypy, pydoc, pytest, then you can't install with pipx.

It is still sort of intermediate still level to realize why it should matter & getting pipx itself installed in the first place (or worse trying to update/replace the python that all the pipx apps are using)

@simon I use it, but rarely. I have maybe 2-3 tools installed using it.