Yes, I understand how to modify the pythonpath, that is not the issue. I am using the site module in that example because it also follows .pth files.
Khabok, I added UWSGI_PYTHONPATH to the directives as a last ditch effort. The CHDIR should take care of it automatically. I believe PYHOME is for specifying the PYTHON_HOME which is used for virtual environments. PYTHONPATH and PYHOME are not interchangeable. Both of these are secondary to the issue at hand. When I try to modify the site path (regardless of how or which pythonpath is currently setup) it blocks uWSGI from doing anything. Commenting out those lines causes it to function immediately. On Tue, Jun 21, 2011 at 3:09 AM, Khabok <[email protected]> wrote: > It was a legibility decision. The append form is less clear at a > glance and I have a personal rule of only using += for numbers. > Performance is REALLY not that important in this case anyway. > Obviously though I didn't read his email as carefully as I thought if > that note seemed helpful when I wrote it. > > > Regarding the problem, isn't UWSGI_PYTHONPATH actually called > UWSGI_PYHOME? The examples page says it is. > > -Schmidty. > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
