I am not aware of the option to make virtualenv make copies of files rather than symlink then, but I would doubt whether it would copy the Python shared library because it needs to be in a location where the operating system can find it. Even if the virtualenv created a physical copy of 'python', then I can't see how removing the system Python version it was dependent on wouldn't break the need of the 'python' executable to find the shared library.
Either way, mod_wsgi itself is compiled for one specific major/minor version of Python. You cannot remove the version it is dependent upon and try and make it use a different version without recompiling mod_wsgi. Graham On 12/05/2014, at 11:45 AM, Scott Schaefer <[email protected]> wrote: > True, but in my case, the virtual environment is completely stand-alone. I > had virtualenv copy the python files instead of symlink to them. The distro > upgrade can overwrite python 3.3 and my virtualenv will remain intact and > functional. So, that being the case, I assume since mod_wsgi was linked > against the shared library, it would then cease to function. I'd have to link > it somewhere else which, from reading the docs, is bad practice. > > On Sunday, May 11, 2014 7:33:21 PM UTC-6, Graham Dumpleton wrote: > Removing the Python installation which the Python virtual environment and > mod_wsgi were dependent on would generally break both. > > On 12/05/2014, at 4:30 AM, Scott Schaefer <[email protected]> wrote: > >> 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]> 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. > > > -- > 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. -- 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.
