Setting Up a New Mac Mini with Python 3.14 using Homebrew

Getting a new Mac Mini feels great until it is time to set up your development environment from scratch.

That was exactly my situation. I wanted a clean Python 3.14 setup on my new Mac Mini, followed by TA-Lib for trading and technical analysis work. Sounds simple enough. But like most real setup journeys, there were a few bumps along the way.

Here is the full step-by-step story of how I got everything working cleanly with Homebrew.

Step 1: Checking if Homebrew was installed

The first thing I needed was Homebrew, the package manager that makes life on macOS much easier.

I checked it with:

brew --version

And confirmed it was installed successfully.

Once Homebrew is ready, installing developer tools becomes much easier.

Step 2: Testing Homebrew with a simple package

Before touching Python, I wanted to make sure Homebrew was working properly.

So I installed wget:

brew install wget

That completed successfully, which confirmed:

• Homebrew was healthy
• Downloads were working
• Bottles were being installed correctly
• My Mac Mini environment was ready for bigger installs

This is actually a nice quick sanity check on a brand-new machine.

Step 3: Installing Python 3.14 with Homebrew

Next, I installed the latest Python 3.14 release available through Homebrew:

brew install [email protected]

The installation completed successfully, and Homebrew showed an important message:

• python3 was installed at /opt/homebrew/bin/python3
• unversioned commands like python and pip were available through:
  /opt/homebrew/opt/[email protected]/libexec/bin

This matters because just installing Python is not enough. Your shell also needs to know where to find it.

Step 4: Updating the shell PATH

To make sure my Mac used the new Homebrew Python instead of the old system Python, I added Python 3.14 to my shell path.

First, I added the main Python binary path:

echo 'export PATH="/opt/homebrew/opt/[email protected]/bin:$PATH"' >> ~/.zprofile
source ~/.zprofile

After that, I checked:

python3 --version

And got:

Python 3.14.3

That was a good sign.

Step 5: Fixing the python command

Even though python3 was working, python still was not:

python --version

Result:

zsh: command not found: python

This happened because Homebrew installs the unversioned shortcuts like python and pip in a separate location.

So I added that path too:

echo 'export PATH="/opt/homebrew/opt/[email protected]/libexec/bin:$PATH"' >> ~/.zprofile
source ~/.zprofile

Then I checked again:

python --version
pip --version

And this time it worked perfectly.

Now both python3 and python pointed to Python 3.14.3.

Step 6: Installing TA-Lib

With Python working, I moved on to TA-Lib.

TA-Lib has two parts:

1. the native C library
2. the Python wrapper

First, I installed the C library through Homebrew:

brew install ta-lib

That part worked immediately.

Then I tried installing the Python package:

python3 -m pip install TA-Lib

And hit this error:

error: externally-managed-environment

This is where a lot of developers get stuck.

Step 7: Understanding the externally-managed-environment error

Homebrew protects its Python installation from direct global pip installs.

That means when you use Homebrew Python, pip install into the system-wide environment is blocked unless you force it.

Why?

Because mixing Homebrew-managed packages and manually installed global Python packages can break your environment.

This is actually a good thing. It pushes you toward a cleaner setup.

The correct solution is to use a virtual environment.

Step 8: Creating a virtual environment for TA-Lib

Instead of forcing a risky global install, I created a dedicated virtual environment:

mkdir -p ~/venvs
python3 -m venv ~/venvs/talib
source ~/venvs/talib/bin/activate

Once activated, I upgraded the package tools inside the virtual environment:

python -m pip install --upgrade pip setuptools wheel

Then I installed TA-Lib again:

python -m pip install TA-Lib

This time it worked.

Step 9: Verifying TA-Lib installation

Finally, I tested the import:

python -c "import talib; print(talib.__version__)"

And got:

0.6.8

Success.

That confirmed:

• the TA-Lib C library was installed
• the Python wrapper was installed
• the virtual environment was working properly
• Python could import the module without errors

Final Working Setup

At the end of the process, my Mac Mini had:

• Homebrew installed and working
• Python 3.14.3 installed via Homebrew
• python3, python, and pip correctly available in the shell
• TA-Lib installed properly inside a virtual environment

That is a clean and reliable setup for trading, scripting, and technical analysis development on macOS.

Complete Commands

Here is the full working sequence in one place:

brew install [email protected]

echo 'export PATH="/opt/homebrew/opt/[email protected]/bin:$PATH"' >> ~/.zprofile
echo 'export PATH="/opt/homebrew/opt/[email protected]/libexec/bin:$PATH"' >> ~/.zprofile
source ~/.zprofile

python3 --version
python --version
pip --version

brew install ta-lib

mkdir -p ~/venvs
python3 -m venv ~/venvs/talib
source ~/venvs/talib/bin/activate

python -m pip install --upgrade pip setuptools wheel
python -m pip install TA-Lib

python -c "import talib; print(talib.__version__)"

Lessons Learned

A fresh Mac setup is never just about installing packages. It is also about understanding how the system, shell, package manager, and Python environment fit together.

Here are the biggest takeaways from this setup:

• Homebrew Python does not automatically make python available unless you add the right path
• Tiny shell typos can look like bigger configuration problems
• Homebrew blocks risky global pip installs for a reason
• Virtual environments are the cleanest way to install Python libraries like TA-Lib
• Once configured properly, the setup is smooth, modern, and reliable

Closing Thoughts

What started as a simple goal – installing Python and TA-Lib on a new Mac Mini – turned into a much bigger exercise in building a clean, reliable development environment.

Along the way, I did much more than just get Python running. I set up the full foundation around it: Homebrew for package management, Git for version control, Node.js and npm for tooling, Redis and PostgreSQL for data and services, Docker for containerized workflows, and Xcode for the complete Apple development toolchain. I also added VS Code as my main editor, along with Claude Code and Codex for AI-assisted algo trading workflows.

The final setup is much better than a messy global install:

• cleaner
• safer
• easier to manage
• better for future trading, quant, and automation projects

And now the Mac Mini is fully ready for running OpenAlgo – OpenSource Self Hosting Algotrading Platform