I'm sorry, I don't recall having issues with sqlite. would you mind sending the centos script for replacing the updated in trunk until we have the 2.7 version working?
El jueves, 2 de agosto de 2012 07:01:17 UTC-3, peter escribió: > > Attached is a working script that uses python2.6. It handles https. > > Python2.7 causes problems, eg no sqlite. This is why my original script > was for python2.6. If anyone actually gets a Python2.7 script that they > have tested on a bare centos 5 machine, then fine submit it. The attached > script has been tested in this manner. > > The only thing my script does not set up is the parameters_443.py file for > the password. I copied this in manually. > > Peter > > On Wednesday, 1 August 2012 18:30:37 UTC+1, Alan Etkin wrote: >> >> >>> I have got through 5 issues on your instructions so far: >>> >>> >>> 'force-reload' not recognised so removed from uwsgi >>> >>> >> Didn't test that command, it came with the example uwsgi startup script, >> but I think there's no need of it >> >> 'tar's had '-zxvf' as options, changed to 'zxvf' >>> >> tar man page examples use dash, perhaps it accepts both syntaxes. >> >> 'cp -R ./$version/* /opt/uwsgi-python/*' >>> >>> changed to >>> >>> 'cp -R ./$version/* /opt/uwsgi-python' >>> >>> >> The second argument of cp is not a valid location. My bad. >> >> >>> after >>> >>> "cd /opt/uwsgi-python >>> >>> echo 'build using python 2.7' >>> python2.7 setup.py build" >>> >>> I get ImportError no module named setuptools. >>> >>> >> The setup script must be trying to import python libraries not installed, >> However, that command is not mandatory for building uwsgi. It should be >> enough to call >> >> python2.7 uwsgiconfig.py --build >> >> If that command builds uwsgi successfully under /opt/uwsgi-python, the >> script start command should work >> >> --
