To install Python on Mac OS cleanly, pick one of four routes — brew install python@3.13 for simplicity, the python.org installer for an official build, pyenv for multiple versions, or uv if you want project tooling included — and then do all real work inside virtual environments. Any of these takes minutes. The reason Python-on-Mac has a reputation for misery is not installation; it is what happens afterward, when three different Pythons fight over your PATH and pip install lands packages somewhere no interpreter looks. This guide gets you a working python 3 install (Mac-specific traps included) and a setup that stays clean.
What your Mac already has (and why you should not use it)
Can you download Python on Mac? You barely need to — but the preinstalled situation is misleading:
- Modern macOS ships no Python 2 (Apple removed it in macOS 12.3, back in 2022). If a tutorial says
python, it is an old tutorial. /usr/bin/python3exists, but it is a stub tied to Apple's Xcode Command Line Tools — the first run may prompt a developer-tools install, the version trails the current Python release, and Apple updates it on Apple's schedule, not Python's.
Treat the system python3 as something for Apple's tooling, not for your development. Every serious how to install Python on MacBook guide starts the same way: install your own.
Route 1: Homebrew (the pragmatic default)
brew install python@3.13
python3.13 --version
Homebrew gives you current versions, easy upgrades (brew upgrade), and multiple minors side by side (python@3.12, python@3.13 coexist happily).
One modern behavior to expect: Homebrew's Python is marked externally managed (PEP 668), so a bare pip3 install requests into the global interpreter is refused with an externally-managed-environment error. This is not a bug — it is the guardrail that keeps your package manager's Python from being mutated into an unreproducible snowflake. The intended workflow is virtual environments (below) or pipx for standalone CLI tools:
brew install pipx
pipx install httpie # isolated, on PATH, upgradeable
Route 2: the python.org installer (official builds)
Download the macOS 64-bit universal installer from python.org, run the .pkg, and you get /usr/local/bin/python3 plus an Applications folder entry. Two post-install notes people miss:
- Run the bundled Install Certificates.command script; without it, the interpreter may fail TLS verification against sites using common CA roots, and you will chase
CERTIFICATE_VERIFY_FAILEDerrors that look like network bugs. - Upgrades are manual — you are back to remembering to download patch releases. Python ships security fixes in every 3.x.y patch; an installer-based Python is only as patched as your diligence.
Choose this route if policy requires official python.org builds; otherwise Homebrew's upgrade story is worth more than the official stamp.
Route 3: pyenv (multiple versions, per-project pinning)
If different projects need different interpreter versions, pyenv is the established answer — it builds and switches full Python versions:
brew install pyenv
# ~/.zshrc
eval "$(pyenv init -)"
pyenv install 3.12
pyenv install 3.13
pyenv global 3.13 # machine default
cd legacy-service && pyenv local 3.12 # writes .python-version
The committed .python-version file gives every teammate (and CI, via pyenv-aware images or setup actions) the same interpreter — the same self-enforcing-documentation pattern as .java-version and .nvmrc.
Route 4: uv (the fast newcomer that does it all)
uv, the Rust-based Python tool from Astral, manages interpreters and dependencies:
brew install uv
uv python install 3.13
uv init myproject && cd myproject
uv add requests # creates .venv automatically, writes lockfile
uv run python main.py
For greenfield work in 2025, uv's combination of interpreter management, automatic virtual environments, and a real lockfile is compelling — lockfiles being the thing that makes builds reproducible and dependency review possible at all.
The one non-negotiable habit: virtual environments
Whichever route installed your interpreter, project dependencies never go into it globally:
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
This is a hygiene rule with a security payoff. Isolated environments plus pinned requirements (or uv/poetry lockfiles) mean you know exactly which package versions each project runs — which is the precondition for knowing when one of them turns up in a vulnerability advisory. PyPI sees a steady stream of malicious and typosquatted packages, and the difference between "we grep one lockfile" and "who knows what is installed globally on forty laptops" is your incident-response afternoon. Continuous dependency scanning automates that lookup — a tool like Safeguard reads the lockfile and flags the vulnerable pin, including transitive ones you never typed.
PATH sanity: the five-minute audit
Most "Python is broken on my Mac" reports are PATH reports. Diagnose with:
which -a python3
python3 -c "import sys; print(sys.executable)"
which -a lists every python3 in PATH order; the first line wins. The rules that keep it sane:
- Know which Python you intend to be default, and make sure its directory precedes the others in PATH (Homebrew's shellenv line typically handles this).
- Never
sudo pip install. Ever. It writes into interpreters other tools depend on. - Do not delete
/usr/bin/python3or anything under/System— it is Apple's, and SIP protects it for good reason. - When a project misbehaves, check
sys.executablefirst — nine times out of ten the venv was not activated.
Keep it patched, and know your version's lifespan
CPython minor versions receive fixes for five years: full bug-fix support for roughly the first two, security-only patches after that, then end of life. Practically: 3.8 reached end of life in October 2024, and each October another minor ages out. Running an EOL interpreter means unfixed CVEs in the interpreter and stdlib — the runtime equivalent of an abandoned dependency, and something worth checking across your services, not just your laptop. Patch cadence:
- Homebrew:
brew update && brew upgrade(routine). - python.org installs: subscribe to release announcements; upgrades are on you.
- pyenv:
pyenv install 3.13picks up new patch releases; rebuild and repoint. - uv:
uv python installfetches current builds.
For a deeper treatment of runtime-and-dependency lifecycle policy, our academy has a track on managing language runtimes across a fleet.
FAQ
Does macOS come with Python already installed?
It ships a python3 stub tied to Apple's developer tools, and no Python 2 at all (removed in macOS 12.3). The bundled python3 lags current releases and updates on Apple's schedule, so developers should install their own via Homebrew, python.org, pyenv, or uv.
What is the easiest way to install Python 3 on a Mac?
brew install python@3.13 if you use Homebrew, or the python.org .pkg installer if you do not. For multiple versions per project, use pyenv; for an all-in-one modern toolchain with lockfiles, use uv.
Why does pip install fail with externally-managed-environment?
Recent Homebrew (and Debian-style) Pythons implement PEP 668, refusing global pip installs to protect the interpreter's integrity. Create a virtual environment (python3 -m venv .venv) for project packages, or use pipx for standalone tools.
How do I check which Python my Mac is actually using?
which -a python3 shows every python3 in PATH order (the first wins), and python3 -c "import sys; print(sys.executable)" shows the exact binary the current interpreter is running from.