Adrian Holovaty wrote:
>
> I must say, I'm really excited about this change. I've been converting
> my own stuff to it, and it feels more natural.
>
I'm not actually using django (yet) but I always wondered why you
weren't using callables directly, it's really more intuitive and
pythonic, what about doing the same inside config files?
For example:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.middleware.doc.XViewMiddleware',
)
becomes:
from django import middleware, contrib
MIDDLEWARE_CLASSES = (
middleware.common.CommonMiddleware,
contrib.sessions.middleware.SessionMiddleware,
contrib.auth.middleware.AuthenticationMiddleware,
middleware.doc.XViewMiddleware,
)
Not the best example of reusability but you get the point. ;-)
Ciao
Michele
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
