OSX 10.5上Python 2.7的Virtualenv路径问题
问题描述
我在尝试加载一个使用了mod_wsgi、Python 2.7和virtualenv的Django网站时遇到了问题。当我在浏览器中访问这个网站时,出现了500错误。查看Apache日志中的错误信息后,我发现了以下内容……
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] mod_wsgi (pid=69270): Exception occurred processing WSGI script '/Volumes/Ontario/Sites/emails/config/apache/dev.emails.wenatcheeworld.com.wsgi'.
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] Traceback (most recent call last):
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] File "/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg/django/core/handlers/wsgi.py", line 230, in __call__
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] self.load_middleware()
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] File "/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg/django/core/handlers/base.py", line 33, in load_middleware
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] for middleware_path in settings.MIDDLEWARE_CLASSES:
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] File "/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg/django/utils/functional.py", line 276, in __getattr__
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] self._setup()
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] File "/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg/django/conf/__init__.py", line 40, in _setup
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] self._wrapped = Settings(settings_module)
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] File "/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg/django/conf/__init__.py", line 75, in __init__
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] raise ImportError("Could not import settings '%s' (Is it on sys.path? Does it have syntax errors?): %s" % (self.SETTINGS_MODULE, e))
[Tue Oct 11 09:32:30 2011] [error] [client 206.130.131.226] ImportError: Could not import settings 'config.settings' (Is it on sys.path? Does it have syntax errors?): No module named config.settings
错误追踪信息让我很困惑,因为加载的文件来自全局的Python 2.5库。
Virtualenv设置信息
我在一台运行OS X 10.5.8的OS X服务器上安装了Python 2.7。我是通过Python 2.7.2 Mac OS X 32位 i386/PPC安装包来安装的。现在服务器上安装的是virtualenv 1.6.4。
我为一个新网站设置了virtualenv,使用了以下命令:
$ cd /usr/local/virtualenvs
$ virtualenv --no-site-packages -p /usr/local/bin/python2.7 dev.emails
然后我安装了所有必要的Python包。当我运行 pip freeze
时,得到的输出是:
$ pip freeze
Django==1.3
PIL==1.1.7
South==0.7.3
amqplib==1.0.2
anyjson==0.3.1
boto==2.0
celery==2.2.7
django-celery==2.2.4
django-compressor==0.9.2
django-grappelli==2.3.4
django-picklefield==0.1.9
feedparser==5.0.1
html2text==3.02
kombu==1.4.1
lxml==2.2.2
psycopg2==2.4.2
pyparsing==1.5.6
python-dateutil==1.5
python-sendgrid==0.2.0dev
redis==2.4.9
requests==0.6.2
wsgiref==0.1.2
故障排除步骤
我创建了一个名为 path_test.py
的脚本来测试我的virtualenv路径……
import os
import sys
# Activate Python Virtual Enviroment
activate_this = '/usr/local/virtualenvs/dev.emails/bin/activate_this.py'
execfile(activate_this, dict(__file__=activate_this))
# start django
import django.core.handlers.wsgi
os.environ['DJANGO_SETTINGS_MODULE'] = 'config.settings'
for p in sys.path:
print p
application = django.core.handlers.wsgi.WSGIHandler()
当我使用 python path_test.py
运行这个脚本时,得到的输出是:
/usr/local/virtualenvs/dev.emails/lib/python2.5/site-packages
/Volumes/Ontario/Sites/emails/bin
/Library/Python/2.5/site-packages/MySQL_python-1.2.2-py2.5-macosx-10.5-i386.egg
/Library/Python/2.5/site-packages/paramiko-1.7.4-py2.5.egg
/Library/Python/2.5/site-packages/simplejson-2.0.7-py2.5-macosx-10.5-i386.egg
/Library/Python/2.5/site-packages/python_ldap-2.3.7-py2.5-macosx-10.5-i386.egg
/Library/Python/2.5/site-packages/lxml-2.2.2-py2.5-macosx-10.5-i386.egg
/Library/Python/2.5/site-packages/pytz-2010h-py2.5.egg
/Library/Python/2.5/site-packages/python_openid-2.2.4-py2.5.egg
/Library/Python/2.5/site-packages/Markdown-2.0.3-py2.5.egg
/Library/Python/2.5/site-packages/django_authopenid-1.0.1-py2.5.egg
/Library/Python/2.5/site-packages/Django-1.2.1-py2.5.egg
/Library/Python/2.5/site-packages/django_profiles-0.2-py2.5.egg
/Library/Python/2.5/site-packages/django_openid_consumer-0.1.1-py2.5.egg
/Library/Python/2.5/site-packages/setuptools-0.6c11-py2.5.egg
/Library/Python/2.5/site-packages/ipython-0.10-py2.5.egg
/Library/Python/2.5/site-packages/httplib2-0.6.0-py2.5.egg
/Library/Python/2.5/site-packages/guess_language-0.2-py2.5.egg
/Library/Python/2.5/site-packages/django_ratings-0.3.4-py2.5.egg
/Library/Python/2.5/site-packages/pip-0.8.1-py2.5.egg
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python25.zip
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-darwin
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/plat-mac/lib-scriptpackages
/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-tk
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-dynload
/Library/Python/2.5/site-packages
/Library/Python/2.5/site-packages/PIL
/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjC
如果我先激活virtualenv,使用 source /path/to/virtualenv/bin/activate
,然后再运行 python path_test.py
,得到的输出是:
/usr/local/virtualenvs/dev.emails/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg
/usr/local/virtualenvs/dev.emails/lib/python2.7/site-packages/pip-1.0.2-py2.7.egg
/usr/local/virtualenvs/dev.emails/lib/python2.7/site-packages/lxml-2.2.2-py2.7-macosx-10.3-intel.egg
/usr/local/virtualenvs/dev.emails/lib/python2.7/site-packages
/usr/local/virtualenvs/dev.emails/lib/python2.7/site-packages/PIL
/Volumes/Ontario/Sites/emails/bin
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/site-packages/pip-1.0.2-py2.7.egg
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/site-packages/lxml-2.2.2-py2.7-macosx-10.3-intel.egg
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python27.zip
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/plat-darwin
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/plat-mac
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/plat-mac/lib-scriptpackages
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/lib-tk
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/lib-old
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/lib-dynload
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/site-packages
/Volumes/Ontario/local/virtualenvs/dev.emails/lib/python2.7/site-packages/PIL
/Volumes/Ontario/Sites/emails
到目前为止,我很确定问题出在virtualenv中的 activate_this.py
没有正确设置 sys.path
。
4 个回答
看起来mod_wsgi默认使用的是Python 2.5。你是不是没有正确编译它?可以看看这个链接:http://code.google.com/p/modwsgi/wiki/InstallationIssues#Multiple%5FPython%5FVersions。
关于virtualenv和mod_wsgi的页面上提到:
注意,从这个基础环境创建的Python版本必须和编译mod_wsgi时使用的Python版本一致。也就是说,不能混用不同主版本或次版本的Python环境。
[1] http://code.google.com/p/modwsgi/wiki/VirtualEnvironments
你遇到了一些问题。
首先,activate_this.py这个文件本身是没问题的。问题出在你的设置上。你想要激活虚拟环境,但你使用的是系统默认的2.5版本的Python,而不是虚拟环境里的2.7版本。这就是你看到系统的库文件的原因;“--no-site-packages”这个选项只对虚拟环境创建的Python有效。这也是为什么它会添加“/usr/local/virtualenvs/dev.emails/lib/python2.5/site-packages”的原因。activate_this.py脚本会根据执行它的Python版本来决定使用哪个库文件目录:
site_packages = os.path.join(base, 'lib', 'python%s' % sys.version[:3], 'site-packages')
当你激活虚拟环境时,它就会使用正确的2.7版本。
其次,你的mod_wsgi版本是基于系统的2.5版本构建的,所以当虚拟环境没有激活时,它会遇到和你看到的同样的问题。“activate_this.py”脚本实际上并没有强制执行“--no-site-packages”这个选项,它依赖的是虚拟环境创建的Python版本,所以mod_wsgi永远不会强制执行“--no-site-packages”。这就是为什么当它在虚拟环境中找不到2.5的库文件目录时,会回退到系统上安装的Django版本。
第三,Apache在10.5上是以64位运行的,而你安装的Python版本只有32位,所以即使你把mod_wsgi重新编译成2.7版本,Apache在尝试加载时也会崩溃。当然,你的所有2.5版本的网站也会遇到和现在2.7版本网站一样的问题。最好的办法是把你的2.7网站放在像gunicorn这样的服务后面运行。
正如我在自己问题的回复中提到的,以及其他人所说的,使用mod_wsgi时无法使用不同版本的Python。我的解决办法是为我需要不同版本Python的特定网站安装和设置gunicorn。
首先,我安装了gunicorn...
$ /usr/local/virtualenvs/my.examplesite/bin/activate
$ pip install gunicorn
然后,我设置了一个launchd.plist文件来运行gunicorn,文件路径是/Library/LaunchDaemons/my.examplesite.com.plist
:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key><string>my.examplesite.com</string>
<key>EnvironmentVariables</key>
<dict>
<key>DJANGO_SETTINGS_MODULE</key><string>config.settings</string>
</dict>
<key>UserName</key><string>_www</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/virtualenvs/my.examplesite/bin/gunicorn_django</string>
<string>--bind=127.0.0.1:8001</string>
</array>
<key>RunAtLoad</key><true/>
<key>StandardErrorPath</key><string>/var/log/gunicorn/my.examplesite.com.error.log</string>
<key>StandardOutPath</key><string>/var/log/gunicorn/my.examplesite.com.access.log</string>
</dict>
</plist>
接下来,我设置了nginx来提供媒体文件,并将请求转发到我的gunicorn服务器:
server {
listen 80;
server_name my.examplesite.com;
access_log /var/log/nginx/my.examplesite.com.access.log;
error_log /var/log/nginx/my.examplesite.com.error.log;
location = /favicon.ico {
return 404;
}
location /static/ {
root /path/to/site/root/;
}
location /media/ {
root /path/to/site/root/;
}
location / {
proxy_pass http://127.0.0.1:8001/;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
}
}