Your Mac already comes with a version of Python, but it's often outdated and deeply integrated into the operating system. Modifying this system Python can lead to unexpected problems. A better approach is to install and manage your own, separate version. The best tool for this on macOS is Homebrew.

Before installing, you might want to check if it's already on your system. You can do this by opening your Terminal app and running the command brew --version.

If it's installed, you'll see a version number. If not, you'll get a "command not found" error. To install Homebrew, paste the following command into your terminal and press Enter. The script will explain what it's going to do and prompt you for your password before it starts.

The installation might take a few minutes. Once it's done, the installer will give you one or two commands to run to add Homebrew to your system's PATH. This is a crucial step that tells your shell where to find the brew command. Go ahead and run those commands now.

With Homebrew ready, installing a modern version of Python is straightforward. You'll use a single command to get the latest stable release.

Homebrew installs Python and its related tools, including pip, the Python package installer. However, your system needs to know to use this version of Python instead of the one that came with macOS. This is handled by configuring your shell's startup file.

On modern macOS, the default shell is Zsh, and its configuration file is .zshrc, located in your home directory (~/). You need to add a line to this file to ensure the Homebrew-installed binaries are found first.

After saving the file, you must either restart your terminal or run source ~/.zshrc for the changes to take effect. Now, when you type python3, your shell will find Homebrew's version in /usr/local/bin before it finds the system version.

You can verify this by checking the path and version:

When you work on multiple Python projects, they often have different dependencies. One web scraping project might need requests version 2.25, while another needs version 2.28. Installing these system-wide can create conflicts. The solution is to create isolated environments for each project using Python's built-in venv module.

Let's create a directory for a new scraping project and set up a virtual environment inside it.

This creates a new folder named env inside my-scraper. This folder contains a copy of the Python interpreter and a place to install project-specific libraries. To use it, you need to activate it.

You'll know it's active because your terminal prompt will change to show (env) at the beginning. Now, any packages you install with pip will be placed inside the env folder, leaving your global Python installation untouched. To deactivate the environment, simply type deactivate.

A best practice for managing dependencies is to use a requirements.txt file. This file lists all the packages your project needs. You can create one and install from it using pip.

This command tells pip to read the specified file and install the exact versions of the packages listed. This makes your project reproducible for anyone who wants to run it. They just need to create their own virtual environment and run the same pip install -r requirements.txt command.

Check your understanding of the key concepts for setting up your macOS environment.

Now that your environment is configured, you have a stable and isolated foundation for building web scraping tools. You can create a new virtual environment for every project, ensuring your dependencies are always managed cleanly.