On 17 April 2010 08:42, cd34 <[email protected]> wrote: > On the page: http://code.google.com/p/modwsgi/wiki/IntegrationWithPylons > > the method used does not work if pylons is installed using a > virtualenv -- which is the suggested method for installing Pylons. > > Important to note, in development.ini, debug=false needs to be set in > the [DEFAULT] section. When set to true, an error 500 is generated > with: > > AssertionError: The EvalException middleware is not usable in a multi- > process environment > > The ./project/data directory within the project also needs to be > writeable by the webserver. > > The minimal script that can be used: > > import sys > import site > > sys.path.append('/path/to/virtualenv/lib') > site.addsitedir('/path/to/virtualenv/lib/python2.5/site-packages') > > from paste.deploy import loadapp > > application = loadapp('config:/path/to/virtualenv/pytest/ > development.ini') > > > /path/to/virtualenv is replaced with the directory created by: > > python go-pylons directory
For virtual environments read: http://code.google.com/p/modwsgi/wiki/VirtualEnvironments What you are doing is not sufficient. Also read: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Browser_Based_Debugger You can still have DEBUG be true, but you must run a configuration whereby all requests go to the same process. On UNIX boxes that means using daemon mode and allowing the default of one process to be used. Don't use 'processes=1' as that is a special case and still results in wsgi.multitoprocess being true, just leave the processes option out all together. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
