Thank you for the explanation. I'll go ahead and try those other few things to verify the configuration.
In the mean time, suppose I upgrade to 14.04, which replaces Python 3.3 with Python 3.4. The shared library that mod_wsgi was linked against may then be gone (Python 3.3 lib). Will this cause it to break even though I'm pointing it to a 3.3 virtualenv? On Saturday, May 10, 2014 10:56:41 PM UTC-6, Graham Dumpleton wrote: > > > On 11/05/2014, at 10:15 AM, Scott Schaefer <[email protected]<javascript:>> > wrote: > > WSGIDaemonProcess mercury user=webuser group=webuser \ > python-home=/home/webuser/projmercury/merc_dev \ > > python-path=/home/webuser/projmercury/merc_dev:/home/webuser/projmercury/merc_dev/lib/python3.3/site-packages > > \ > display-name=%{GROUP} > > > And you don't need to > list /home/webuser/projmercury/merc_dev/lib/python3.3/site-packages in > python-path. If all is okay you having set python-home to the value of the > sys.prefix for that Python installation/virtual environment should be > enough for the site-packages from that installation to be used. > > Graham > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
