The most important macOS distinction is processor architecture. Intel and Apple Silicon systems may use different native binaries, and some packages may need compatible wheels or build tools. Identify the machine before installing dependencies that include compiled code.
Do not treat the system-provided Python as your project environment. Install a supported Python version, verify the shell command, and create a virtual environment for each project. Configure the editor to use that environment and test a package that represents the project’s real workload.
If the terminal and editor disagree, compare their executable paths and shell startup files. Avoid adding multiple competing PATH entries without understanding their order. When a package fails to install, check architecture compatibility, available build tools, and the package’s current support. A simple, documented setup is easier to maintain than a collection of global fixes.