elias.collas at gulfstream.com
elias.collas at gulfstream.com
Mon Nov 5 17:06:38 EST 2007
Thanks for the great suggestion. I'll give that a try. "Graham Dumpleton" <graham.dumpleton at gmail.com> wrote on 11/05/2007 04:54:09 PM: > A fiddle that should work is for you to create using Ian Bicking's > virtualenv package a distinct Python installation based on your > current one and then install in that all the required new packages you > want to use, including mod_python site-packages components. Then, in > the 'envvars' file in the same directory as your Apache httpd > executable add: > > PYTHONHOME=/some/path/env > export PYTHONHOME > > That path should refer to the top directory created by the virtualenv tool. > > The Python code when being initialised will see PYTHONHOME and will > use that separate virtual environment as the source of all the Python > modules and not your main installation. > > For information on virtualenv see: > > http://pypi.python.org/pypi/virtualenv > > Graham
|