On 01/11/2014, at 3:37 PM, YKdvd <[email protected]> wrote: > Thanks, yes, I've discovered that although the original box had the > virtualenv in a /home directory as well, that one had been monkeyed with to > have world-readable permissions. On the new box the home directory had the > standard non-readable permissions, so www-data can't read it. I'll get this > fixed up, probably move the venv somewhere else readable by www-data. > > Do normal use-cases of modwsgi depend on the fallback to the default Python > when an explicitly-specified python-home is given? I'd think it would be > problematic in many cases. Perhaps at least issuing some sort of diagnostic > warning would be useful?
The behaviour of ignoring a directory if it doesn't appear to be a valid Python installation is an attribute of how the Python interpreter initialisation. To try and validate it would mean mod_wsgi having to replicate what Python does and that is a huge can of worms because of the horrible algorithm it uses along with all the platform specific variations. I am not even sure I can reliably check sys.prefix against what was expected because technically it can still be different. Most perhaps can do is check whether the directory is accessible and issue a warning if it isn't. 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.
