Should I use Homebrew to install Python?

Homebrew ships Python because dozens of its own packages depend on it. Tools like glib, cmake, and awscli all pull in Python as a build or runtime dependency. When Homebrew installs Python, it is satisfying its own dependency graph, not setting up a development environment for you.

This distinction matters because Homebrew treats Python the same way it treats any other dependency: as something to keep current. Running brew upgrade can bump Python from 3.12 to 3.13 without warning, and that upgrade removes the previous minor version’s site-packages directory. Any packages installed with pip into that Homebrew-managed Python vanish. Virtual environments that were linked against the old interpreter break with errors like dyld: Library not loaded or No such file or directory: python3.12.

How Homebrew manages Python versions

Homebrew maintains a single “current” Python formula (python@3.x) plus versioned formulae for older releases that active packages still need. When the core formula advances, Homebrew rebuilds every dependent formula against the new version and removes the old one on cleanup. Developers who happened to be using that Python for their own projects lose their setup as a side effect of routine maintenance.

Homebrew also does not support installing patch-level versions. You can install python@3.12, but you cannot pin to Python 3.12.4 specifically. For projects that need reproducible builds or must match a production interpreter exactly, Homebrew offers no mechanism to do so.

The pip install trap

Because brew install python puts a python3 binary on your PATH, many developers start using it to install packages globally with pip install. This creates a fragile setup for two reasons:

1. Global pip install puts packages into Homebrew’s site-packages directory, which Homebrew may wipe on upgrade.
2. If Homebrew’s Python version advances, scripts with #!/usr/bin/env python3 shebangs now point to a different interpreter that lacks the previously installed packages.

Using a virtual environment avoids the second problem, but environments created against a Homebrew Python still break when Homebrew removes that Python version.

What to use instead

uv can install and manage Python versions independently of Homebrew. It downloads pre-built interpreters in seconds, supports pinning exact versions (including patch releases), and works across macOS, Linux, and Windows. Because uv manages its own Python installations, a brew upgrade will never interfere with your development environment.

For projects that need a specific Python version, a .python-version file lets uv (and other tools like pyenv) automatically select the right interpreter per project.

Learn More

• How to install Python with uv
• How to switch from pyenv to uv for managing Python versions
• How do pyenv and uv compare for Python interpreter management?