On Jan 7, 2006, at 6:54 AM, kmh wrote:
As Aaron says, it is not obvious to the outsider what the underlying
structure of the package hierarchy is. I suspect this is a common
problem in projects that have evolved to meet the needs of a busy
production environment.
Yeah, this is a very good point.
I'm slightly against the namespace churn you suggest (e.g.
"django.core.exceptions" -> "django.errors") simply because one man's
"intuitive" is another's "confusing." No matter how we rename stuff,
with a package as big as Django someone is always going to think we
named it wrong.
One altertative to your proposal that Adrian and I tossed around at
one point was to alias certain "normal" modules into a set of
"tasks." That way writing a view would become::
from django.tasks.views import *
def view(request):
return render_to_response(....)
And writing a template tag::
from django.tasks.templatetags import *
Etc.
Hm?
Jacob
