On 1/8/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 1/7/06, kmh <[EMAIL PROTECTED]> wrote: > > django.utils.httpwrappers -> django.http > > +1. I'm a big fan of this. django.http would get that'd get the > current contents of django.utils.httpwrappers, plus the Http404 and > Http500 exceptions.
I've got a patch ready to commit that moves django.utils.httpwrappers to django.http and updates all the dependencies and docs. I'd move Http404 in another commit. Also, if we are going to rename the classes in here, (as suggested by Kieran in the last email) I'd do that in a sepatate commit as well. No one has commented on that though. I can't think of any reason to do django/http/__init__.py vs django/http.py other than the former looks more like everything else in django/. Adrian or Jacob, what's your preference, and should I go ahead and commit it? Joseph
