BTW, one of the possible causes of your problem could be the use of a
third party C extension module that doesn't work properly for multiple
sub interpreters. Yes, I know that Trac may be running with
WSGIApplicationGroup of %{GLOBAL}, but if that same C extension module
is being used in Django
Thank you, thank you, thank you! I'll give this a try tonight and see
how long before someone tells me Trac is down. :-)
On Mon, Oct 6, 2008 at 9:08 PM, Graham Dumpleton
[EMAIL PROTECTED] wrote:
2008/10/7 Todd O'Bryan [EMAIL PROTECTED]:
I think you may have hit the nail on the head. The
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
Sorry, but where do I look for the stack trace?
I did find this in the error_log, but it's weird because I'm using
Ubuntu with the package system, so it really should have sorted this
out, I think.
[Mon Oct 06 00:42:39 2008] [warn] mod_wsgi: Compiled for Python/2.5.1.
[Mon Oct 06 00:42:39 2008]
