Here are the relevant parts of my httpd.conf file, I think. WSGIScriptAlias /trac /srv/trac/trac.wsgi <Location /trac> WSGIApplicationGroup %{GLOBAL} </Location>
# <Location "/trac"> # SetHandler mod_python # PythonInterpreter main_interpreter # PythonHandler trac.web.modpython_frontend # PythonOption TracEnvParentDir /srv/trac # PythonOption TracUriRoot /trac # </Location> <LocationMatch "/trac/[^/]+/login"> AuthType Basic AuthName "Trac" AuthUserFile /srv/trac/.htpasswd Require valid-user </LocationMatch> On Sun, Oct 5, 2008 at 8:31 PM, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > 2008/10/6 Todd O'Bryan <[EMAIL PROTECTED]>: >> >> I just started hosting some Mercurial repositories on my server with >> mod_wsgi, and, maybe coincidentally, my Trac setup has started >> throwing the very popular RuntimeError: instance.__dict__ not >> accessible in restricted mode. >> >> Since it had never done that before, I thought the problem might be a >> problem with mod_wsgi and mod_python, so I switched Trac to use >> mod_wsgi, and the problem still shows up. >> >> I'm currently hosting a couple of Django apps and some SVN repos on >> the same server, so it could be stupidity on my part, but I haven't >> seen any reports of mod_wsgi causing this problem on Trac, so I >> suspect there may be a subtle problem. >> >> Any ideas? > > What are you setting WSGIApplicationGroup directive to? See: > > > http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Multiple_Python_Sub_Interpreters > > Graham > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---