Yes thats exactly what i did , a correct -H (or virtualenv) option
On Fri, Nov 9, 2012 at 2:23 AM, Łukasz Czuja <luk...@czuja.pl> wrote: > Hmm... shouldn't you be using --virtualenv option? pointing to projects > virtualenv top directory > > site.py is responsible for setting up python paths. this is basically what > activate/deactivate scripts depend on > > check also sys.prefix/sys.real_prefix and what they point to > > W dniu 08.11.2012 14:59, Phyo Arkar pisze: > > This is more uwsgi problem so here: > > I am doing a self contained , relocatable , standalone python build with > uwsgi, web2py , scipy (Numpy,matplotlib) > > Everything works fine in relocatable enviorment but Uwsgi is having this > error : > > uwsgi socket 0 bound to UNIX address /home/uwsgi/uwsgi/uwsgi.sock fd 3 > Python version: 2.7.2+ (default, Dec 1 2011, 02:17:49) [GCC 4.6.2] > Set PythonHome to ./web2py > ImportError: No module named site > > Here is my uwsgi config : > > #!/bin/bash > ./runtime/bin/uwsgi --http :8000 --chdir ./web2py/ --python-path ./web2py/ > --module uwsgihandler \ > -p 6 --post-buffering 65535 \ > --close-on-exec --socket-timeout 6000 \ > > > Directly running web2py works perfectly fine. > > Any ideas? ALso its seems running python using system python , anyway > to force it to use Custom built python? > > > _______________________________________________ > uWSGI mailing > listuWSGI@lists.unbit.ithttp://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > -- > Pozdrawiam, > > Łukasz Czuja > > Programista / Analityk / Architekt IT > > --
