2011-09-14 39 views
3

我終於解決了普遍存在的MySQL-蟒/ OSX(10.7 64位)的崩潰和已Python和MySQL的使用32位MySQL和主叫用蟒 '拱-i386' 工作正常。外面的Django的PY腳本正確查詢的MySQL等。然而,當我嘗試使用64位的Python的時候火起來Django和調用開發服務器,我得到我以前得到的錯誤:強制Django的使用32位的Python

django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_mysql.so, 2): no suitable image found. Did find: 
    /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_mysql.so: mach-o, but wrong architecture 

在我的.bash_profile我有

別名蟒蛇= '拱-i386 python2.7'

出口VERSIONER_PYTHON_PREFER_64_BIT =沒有

出口VERSIONER_PYTHON_PREFER_32_BIT = YES

所以我不明白Django是如何調用python的,爲什麼它不尊重我在.bash_profile中的內容。我需要在Django中更改它來調用32位Python嗎?當我做「蟒蛇manage.py runserver命令」完整回溯是:

Traceback (most recent call last): 
    File "manage.py", line 14, in <module> 
    execute_manager(settings) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/core/management/__init__.py", line 438, in execute_manager 
    utility.execute() 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/core/management/__init__.py", line 379, in execute 
    self.fetch_command(subcommand).run_from_argv(self.argv) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv 
    self.execute(*args, **options.__dict__) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/core/management/base.py", line 209, in execute 
    translation.activate('en-us') 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/translation/__init__.py", line 100, in activate 
    return _trans.activate(language) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 202, in activate 
    _active.value = translation(language) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 185, in translation 
    default_translation = _fetch(settings.LANGUAGE_CODE) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 162, in _fetch 
    app = import_module(appname) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module 
    __import__(name) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/contrib/admin/__init__.py", line 3, in <module> 
    from django.contrib.admin.helpers import ACTION_CHECKBOX_NAME 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/contrib/admin/helpers.py", line 3, in <module> 
    from django.contrib.admin.util import (flatten_fieldsets, lookup_field, 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/contrib/admin/util.py", line 1, in <module> 
    from django.db import models 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/__init__.py", line 78, in <module> 
    connection = connections[DEFAULT_DB_ALIAS] 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/utils.py", line 93, in __getitem__ 
    backend = load_backend(db['ENGINE']) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/utils.py", line 33, in load_backend 
    return import_module('.base', backend_name) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module 
    __import__(name) 
    File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 14, in <module> 
    raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e) 
django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_mysql.so, 2): no suitable image found. Did find: 
     /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_mysql.so: mach-o, but wrong architecture 

回答

1

VERSIONER_PYTHON_PREFER_32_BIT環境變量是蘋果提供的功能。它僅適用於Mac OS X 10.6和10.7中由Apple提供的系統Pythons。從所示的路徑中,您使用的是非系統Python(安裝在/Library/Frameworks中,可能來自python.org安裝程序)。 VERSIONER_PYTHON_PREFER_32_BIT對它沒有影響。您是否嘗試過的東西,如啓動開發服務器:

arch -i386 /usr/local/bin/python2.7 django-admin.py ... 

您仍可能會遇到麻煩,如果Django的啓動子進程中,將默認爲64位Python解釋。你應該讓所有的東西都能在64位模式下工作,或者堅持一個完整的32位的Python和MySQLdb鏈。通過安裝來自第三方分銷商如MacPorts或Homebrew的完整解決方案,您可以節省很多麻煩。

0

我有一個similar issue with Snow Leopard,但使用的虛擬環境對於我所有的工作。如果你也使用了一個(這是推薦使用Django的方法),那麼你可以強制你的虛擬環境使用的python版本。當你創建一個新的虛擬環境,就這樣說:

virtualenv --python=/Library/Frameworks/Python.framework/Versions/2.7/bin/python new-environment 
+0

這似乎是最好的路線走,但創建的virtualenv並指定自定義路徑蟒蛇後,我仍然得到基本相同的問題,這對我沒有意義。在virtualenv中,在使用python可執行文件去掉x86_64之後,我啓動了交互式shell並驗證sys.maxint是否提供了32位數字。在shell中,我可以無誤地導入MySQLdb和import _mysql。但退出python shell並運行'python manage.py runserver'會導致OP中的Traceback錯誤_mysql.so'錯誤的體系結構'。對我沒有意義。 – kasceled

+0

此lipo解決方法是通過SO線程[here](http://stackoverflow.com/questions/2088569/how-do-i-force-python-to-be-32-bit-on-snow-leopard-and -other-32-bit-64-bit-questi),由用戶Cogg – kasceled

+1

hmm。如果你沒有綁定到MySQL,我會建議轉移到Postgres,因爲這正是Django開發者推薦的。我在使用MySQL幾個月的時候遇到了各種MySQL問題,現在我決定遷移到Postgres,現在我感到很高興。 – Spike