Malcolm Tredinnick wrote: > As a general process, I'm inclined to think it's the wrong direction -- > making namespaces larger and larger. That way lies PHP or web2py.
Having read your replies in this thread I refrain from speaking about general directions :-). This one was about particular issue of two http-related modules. > You > can already write > > from django.view.decorators import http as decs > from django import http > > and it's two short lines. I think, though, that this shows the real > problem: we have a few overlapping names like this that are unfortunate > and historically entrenched. Yeah this was the main point. I understand that views.decorators.http dates back to first release of Django and that django.http was initially just a container for HttpRequest and HttpResponse. But now I think it's more convenient to have just one module for all HTTP-related mechanics. We already have plenty utils in django.http, why not merge two decorators into them? > Working out > how to jam things together won't result in everybody being pleased in > any case. Pleasing everybody is never the goal. It is unreachable whether we do anything at all or not :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
