5 ms·
I use pipx for this. It isolates each tool in its own virtualenv. You might still have to install a specific Python version (although the latest 3.X works fine
by saila 5y ago
I use pipx for this. It isolates each tool in its own virtualenv. You might still have to install a specific Python version (although the latest 3.X works fine for me), but it takes some of the pain out of the process and makes sure you don't pollute your global/system install.
On a Mac, it could be as simple as (assuming you already use Homebrew):
brew install python
brew install pipx
pipx ensurepath # adds ~/.local/bin to $PATH
pipx install <tool>
<tool>
- gullevek 5y agoThat is all nice. And then python updates from 3.9.n to 3.9.n+1 and nothing works anymore. brew sucks with python.
- saila 5y agoI've only run into issues like this when upgrading from Python 3.X to 3.Y, which is to be expected, and Homebrew lets you install a specific 3.X (e.g. brew install python@3.9) if you don't need/want be on the latest version.
- ldrndll 5y agoThanks, I didn’t know about pipx. If it works as advertised that will be a huge improvement for me!
- oars 5y agopipx looks fantastic, thanks for sharing.
- Too 5y agoPipx is really one of the best things that has happened to Python recently. Taking away all the headaches of manually managing venvs. They should integrate it into mainline imo.