MacOS下Python3.6.5导入包提示ImportError的排查求助

Let’s walk through the key checks to resolve this import issue—macOS’s multiple Python versions and path quirks are almost always the culprit here, even after reinstalling via Homebrew.

Next Troubleshooting Steps #

• Verify your Python interpreter and pip3 are aligned
  macOS comes with a system Python, plus any versions you’ve installed via Homebrew, pyenv, or other tools. It’s easy to end up with a mismatch where pip3 installs packages to one Python version, but you’re running a different one.

  • Run which python3 and which pip3—their paths should match (e.g., both pointing to /usr/local/bin/python3 or /opt/homebrew/bin/python3 if you’re on Apple Silicon).
  • List installed packages for your active Python with python3 -m pip list—confirm the package XXXXXX appears here.
  • Check Python’s module search path with python3 -c "import sys; print('\n'.join(sys.path))"—make sure the directory where your package is installed shows up here.

• Check where pip3 is installing your packages
  Use pip3 show XXXXXX to get the Location field (e.g., /usr/local/lib/python3.6/site-packages). Compare this path to the sys.path output from the step above. If it’s missing, that means your Python interpreter isn’t looking in the right place for the package.

• Rule out virtual environment mismatches
  If you’re using virtual environments (venv, virtualenv, etc.), you might have installed the package in one environment but are running Python in another (or no environment at all).

  • Check if you’re in an active virtual environment with echo $VIRTUAL_ENV—if this returns a path, your packages are installed there. If you’re not in the environment, activate it first (e.g., source /path/to/venv/bin/activate).
  • If you didn’t intend to use a virtual environment, ensure you’re installing packages to the global Python with pip3 install XXXXXX (without any virtual env active).

• Confirm you’re actually running Python 3.6.5
  Homebrew’s reinstall python command will typically install the latest stable Python version (not 3.6.5, which is quite old). It’s possible you have multiple Python 3 versions installed, and python3 is pointing to a newer one (like 3.9 or 3.11) while you think you’re using 3.6.5.

  • Run python3 --version to confirm the version. If it’s not 3.6.5, you’ll need to specify the full path to your 3.6.5 interpreter (e.g., /usr/local/bin/python3.6) when running scripts or installing packages (e.g., /usr/local/bin/python3.6 -m pip install XXXXXX).

• Check for permission-related installation issues
  Sometimes pip3 installs packages to your user directory (instead of the system-wide site-packages) if you don’t have admin rights, or if you used the --user flag.

  • Run python3 -m site --user-site to get your user-specific package directory. Compare this to the Location from pip3 show XXXXXX—if they match, ensure your Python interpreter has access to this path (it should by default, but sometimes permission errors can hide packages).
  • If you accidentally used sudo pip3, you might have installed packages with root permissions that your regular user can’t access. Try reinstalling the package without sudo: pip3 install --force-reinstall XXXXXX.

• Double-check the import name vs. package name
  Even if you’re using lowercase, some packages have different import names than their PyPI package names. For example:

  • Install with pip3 install python-dateutil, import with import dateutil
  • Install with pip3 install mysql-connector-python, import with import mysql.connector
    Double-check the package’s documentation to confirm the correct import syntax—this is a sneaky gotcha that’s easy to miss.

内容的提问来源于stack exchange，提问作者YiLuo