Raspbian下dlib导入异常咨询：交互模式正常但运行脚本报错

Hey there, let's work through this frustrating dlib import issue you're hitting. Your hunch about Python 2 vs Python 3 conflicts is totally on the money—this is super common on Raspbian since it still defaults to Python 2 for the python command. Here's how to diagnose and fix it:

1. Make sure you're running your script with the virtual environment's Python #

When you run python your_script.py directly, there's a good chance it's calling the system-wide Python 2 instead of your virtual environment's Python 3.5. Here's how to confirm and fix this:

• First, activate your virtual environment like usual:

  source /path/to/your/venv/bin/activate
  

• Check what python points to now by running:

  which python
  

  It should show a path inside your virtual environment (e.g., /home/pi/venv/bin/python), not /usr/bin/python (which is Python 2 on Raspbian).
• Run your script using this explicit path, or just use python3 (since your venv is tied to Python 3.5):

  python your_script.py
  # OR
  python3 your_script.py
  

2. Add a shebang line to your script #

To avoid having to remember to specify the right Python every time, add this line at the very top of your .py file:

#!/usr/bin/env python3

Then make the script executable:

chmod +x your_script.py

Now you can run it directly with ./your_script.py, and it'll use the Python 3 from your activated virtual environment.

3. Double-check dlib is actually installed in your virtual environment #

Sometimes it's easy to accidentally install packages outside the venv. Verify dlib is present by running these commands with your venv activated:

pip list | grep dlib
# Or more directly:
python -c "import dlib; print('dlib imported successfully! Version:', dlib.__version__)"

If this throws an error, reinstall dlib in your activated venv:

pip install dlib opencv-python

4. Confirm your virtual environment was created with Python 3 #

If you created your venv using just python -m venv venv, it might have used Python 2 (since that's Raspbian's default). Next time, explicitly specify Python 3 when creating the venv:

python3 -m venv venv

This ensures the venv is tied to Python 3.5 from the start.

Most of the time, the issue boils down to running the script with the wrong Python interpreter. Give these steps a try, and you should have dlib working in your script in no time!

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