so while python-oops-wsgi should totally work with django, that may require either a) django changes to be wsgi compliant, or b) some thing django specific.
In b) I think we'd want a new python-oops-django module (heck we may want that anyway) so this bug really isn't relevant to pure -wsgi. Closing its task here, future decisions can be future decisions :)
so while python-oops-wsgi should totally work with django, that may require either a) django changes to be wsgi compliant, or b) some thing django specific.
In b) I think we'd want a new python-oops-django module (heck we may want that anyway) so this bug really isn't relevant to pure -wsgi. Closing its task here, future decisions can be future decisions :)