 Python programmers: do you habitually use pipx to install new tools written in Python? Anonymous poll
Poll
Yes, I use pipx
51
25.8%
No, I don't use pipx
90
45.5%
I don't know how to use pipx
198 people voted. 57
28.8%
Voting ended 13 Jul 2023 at 19:27. 10 comments
@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 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)  @mistersql @simon Yeah, usually I install things like mypy on a per-project basis (e. g. as dev-dependencies). As an added benefit it makes it easier to enforce processes across the whole team (and everybody uses the same version, which means less surprising non-reproducible bugs). |
Gregory's Server
@simon I have historically, but I've recently started trying out 'rye' instead.