2 ms·
I didn't know this about homebrew. Is this only true for installing homebrew python packages? To be honest, I would `brew install python3` or whatever, then ma
by gcr 3y ago
I didn't know this about homebrew. Is this only true for installing homebrew python packages?
To be honest, I would `brew install python3` or whatever, then manage my own per-project virtual environments with direnv, so I'd bypass all of homebrew's efforts to encapsulate and package python packages...
- nerdponx 3y agoIt's at the discretion of the package maintainer, but it's pretty common. Just look at the `Formula.rb` for any standalone app in Python or Lua. Example: https://github.com/Homebrew/homebrew-core/blob/66c42fbd814b3a0c291fb872a569abc441747685/Formula/l/locust.rb#L26-L129 https://github.com/Homebrew/homebrew-core/blob/66c42fbd814b3... I think using per-project venv is still the sensible thing to do, not just in Python but using the equivalent in Lua (hererocks), Ruby (Bundler), etc. This is for system-wide installations of standalone CLI tools and other "apps". However if you do find something on PyPI that is a standalone app, but isn't in Homebrew, you can create an isolated env for it automatically using Pipx https://pypa.github.io/pipx/ https://pypa.github.io/pipx/.