OSX环境下无法升级python-dateutil及Sphinx安装配置遇阻求助

Hey Nick, let's work through all your macOS Python/Sphinx headaches one by one—this stuff can get messy when mixing system tools and third-party managers, but we'll clean it up:

Let's get this out of the way first because it's the root of most of your issues. Python 2.7 has been end-of-life since 2020—no security updates, no new package support. Unless you're stuck maintaining a legacy project that only works on 2.7, go with Python 3.X (3.10+ is ideal, since it's stable and widely supported). All modern tools like Sphinx are actively maintained for 3.X, so you'll save yourself future pain.

The reason you can't upgrade python-dateutil is almost certainly because you're trying to modify macOS's system Python. Apple locks down the system Python to prevent breaking core OS functionality, so you'll get permission errors or unexpected behavior if you try to upgrade packages there.

The fix? Never use the system Python for your projects. Use a virtual environment to isolate your dependencies:

• First, install virtualenv (if you haven't already) with the Python version you want to use:

  # For Python 3.X (install via homebrew first if you don't have it)
  pip3 install virtualenv
  

• Create a new virtual environment for your Sphinx project:

  # Replace "sphinx_env" with whatever name you want
  virtualenv -p python3 sphinx_env
  

• Activate the environment (this is key—all subsequent commands will use this isolated Python):

  source sphinx_env/bin/activate
  

• Now upgrade python-dateutil (or install any package) without permission issues:

  pip install --upgrade python-dateutil
  

Stop jumping between macports, homebrew, and wheels—stick to one toolchain, and virtualenv will keep things clean. Now that you have your virtual environment activated:

• Install Sphinx directly via pip (this is the official recommended method):

  pip install sphinx
  

• You can now follow the Sphinx setup guide normally—all dependencies will be contained within your sphinx_env environment, so no conflicts with system tools or other projects.

Pro tip: If you ever need to exit the virtual environment, just run deactivate in your terminal.

Your PYTHONPATH isn't showing up as expected for a few possible reasons:

1. You're modifying the wrong bash config file: On macOS, Terminal loads ~/.bash_profile by default, not ~/.bashrc. Double-check you added the export line to ~/.bash_profile.
2. You didn't reload the config: After editing the file, you need to apply the changes immediately with:

   source ~/.bash_profile
   

3. Your python command points to a different Python version: The path you added is for Python 2.7, but if your python command is actually pointing to Python 3.X (from homebrew, for example), that path won't be in its sys.path. Verify which Python you're using:

   which python
   

   If it's pointing to /usr/local/bin/python (homebrew's Python), use this command to find its correct site-packages path instead:

   python -c "import site; print(site.getsitepackages())"
   

4. You don't need to set PYTHONPATH at all: When using virtualenv, the environment automatically adds its own site-packages directory to sys.path—manual PYTHONPATH overrides can cause confusion. If you stick to virtual environments, you can probably remove that export line from your bash config entirely.

To confirm it's working, after sourcing your bash profile, run:

python -c "import sys; print('\n'.join(sys.path))"

You should see your /usr/local/lib/python2.7/site-packages path listed if you're using Python 2.7.

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