search

etianen / django-watson

Full-text multi-table search application for Django. Easy to install and use, with good performance.
BSD 3-Clause "New" or "Revised" License
1.21k stars 129 forks source link

ImportError: No module named 'watson' #199

Closed josefnorlin closed 7 years ago

josefnorlin commented 7 years ago

Hi, I like what I see about this project!

I'm trying to set up django-watson with Django 1.10.1, but I get: ImportError: No module named 'watson' Am I wrong thinking it will work with Django 1.10:1 when I read its compitable with Django 1.8+?

Or am I doing something else wrong?

etianen commented 7 years ago

I don't think you've installed it correctly. That error implies that you've not installed it as a python module.

Did you follow the instructions here?:

https://github.com/etianen/django-watson/wiki

josefnorlin commented 7 years ago

Thanks for such a quick response! I did follow the instructions (twice and thrice) but after the 3 below I still got my "ImportError: No module named 'watson'"-error.

1) Install django-watson using pip: pip install django-watson. 2) Add 'watson' to your INSTALLED_APPS setting. 3) Update your Database: Django >=1.7: Run the command manage.py migrate.

I did notice that while doing pip install django-watson it placed it in: /usr/local/lib/python2.7/dist-packages, which I seem is odd since I'm running python 3.5. Tried to do the same and tried 'pip3 install django-watson', the files then got placed in /usr/local/lib/python3.5/dist-packages but the error still occurred.

Is there anything more I can try? Seems I'm stuck as I see it now.

josefnorlin commented 7 years ago

Actually, it got solved by adding the PYTHONPATH to my venv/bin/activate file by adding this line:

export PYTHONPATH="/usr/local/lib/python3.5/dist-packages"

I thought that was handled automatically in the virtualenv but apparently not (or maybe I somehow got it erased): But all well and sound now. Hope this can help someone else too.

etianen commented 7 years ago

This should have been handled automatically by the virtualenv. I suspect something is screwy in your dev environment.

Still, I'm glad you found a solution!

On Tue, 25 Apr 2017 at 22:09 Tuxedo Joe notifications@github.com wrote:

Actually, it got solved by adding the PYTHONPATH to my venv/bin/activate file by adding this line:

export PYTHONPATH="/usr/local/lib/python3.5/dist-packages"

I thought that was handled automatically in the virtualenv but apparently not (or maybe I somehow got it erased): But all well and sound now. Hope this can help someone else too.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/etianen/django-watson/issues/199#issuecomment-297165668, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJFCO-IGjDN8e1MWGV2i768O1U4OKleks5rzmD8gaJpZM4NGs6L .