On Aug 5, 9:15 pm, Adam Vollrath wrote:
> I'm not sure what the root cause of this is, and I'm really just glad
> it's working again. I'm willing to do more troubleshooting if
> prompted by list members. Perhaps setting django.root to be just a /
> was a bad cal
I, too, saw this exact stack trace, but when using mod_python. The
error did not appear when using the built-in "runserver". Also, it
only occurred when requesting a URL beyond the root /. This
distinction led me to review my VirtualHost configuration, and I
commented out the following line:
Py
