uwsgi configuration hints to deploy django build with djangorecipe about djangorecipe HOT 3 CLOSED

It looks like you're mixing virtualenv/pip and buildout in some way. Perhaps you're installing uwsgi globally? It looks like it because of all those system directories. Especially something like "lib-tk" wouldn't ever be added by buildout.

I'm not using uwsgi but gunicorn (which is similar). My project's setup.py has a dependency on gunicorn, so buildout installs it for me. With bin/gunicorn I can therefore run the wsgi file just fine.

Would that help?

from djangorecipe.

Sorry for not being clear. Buildout is just doing things correctly in my opinion and bin/django shell has the path correctly set with no system paths.

The path is added by uwsgi. To see those files (added to the sys.path collected by buildout) I had to print them from within the django.wsgi file.

The way I produce it is that I create an empty virtualenv mkvirtualenv -p /usr/bin/python2 base (or equivalent for py3) and use the python interpreter in that virtualenv to run 'python boostrap.py'.

uwsgi has an option to use a virtualenv, that clearly I cannot use as my virtualenv (base2) would be almost empty, so I declare the wsgi_file as shown above. It seems as if in this case the uwsgi process is not isolated from the system python env. In particular I'm using uwsgi in the emperor-vassals configuration.

from djangorecipe.

I solved the issue by adding the virtualenv directive. More explanation in the same issue opened in the buildout as reported above. Thanks for the attention.

from djangorecipe.