python - Running fabric script throws ImportError: No module named celery -
i've been tearing hear out quite time now.
- i in virtualenv , have
celery==3.1.9installed there. - i have default celery/django setup (http://celery.readthedocs.org/en/latest/django/first-steps-with-django.html) , working fine.
as run fabric scripts throws importerror: no module named celery originating proj/proj/celery.py file. going on?
full traceback:
traceback (most recent call last): file "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 658, in main docstring, callables, default = load_fabfile(fabfile) file "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 165, in load_fabfile imported = importer(os.path.splitext(fabfile)[0]) file "/home/username/projects/proj/fabfile/__init__.py", line 2, in <module> .staging import * file "/home/username/projects/proj/fabfile/staging.py", line 3, in <module> proj.settings.staging import domain, ip, user, password file "/home/username/projects/proj/proj/__init__.py", line 5, in <module> .celery import app celery_app file "/home/username/projects/proj/proj/celery.py", line 3, in <module> celery import celery importerror: no module named celery edit: don't think contents of fabric scripts have it. sake of example set:
from fabric.api import local def foo(): local('echo bar') calling fab foo raises importerror: no module named celery. if call fab result same.
my proj/proj/__init__.py:
from __future__ import absolute_import # make sure app imported when # django starts shared_task use app. .celery import app celery_app just in celery tutorial
edit:
this works:
(venv)rg@dfi:~/projects/proj$ python python 2.7.4 (default, sep 26 2013, 03:20:26) [gcc 4.7.3] on linux2 type "help", "copyright", "credits" or "license" more information. >>> celery import celery >>>
a workaround install system-wide celery, not desired behavior of fabric.
Comments
Post a Comment