On 8/11/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Fri, 2006-08-11 at 11:52 +0000, Michele Cella wrote: > > Adrian Holovaty wrote: > > 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', ... > There's a bit of a chicken-and-egg problem here in the current > implementation. Many MIDDLEWARE_CLASSES and INSTALLED_APPS require > certain values from settings. Importing them when settings is not fully > imported will lead to lots of problems.
Don't you have the same problem with views? That is, you'd need to import a view's module before getting a reference to the callable, and that module might need settings. If that's OK because it's just less likely to occur, well, OK. I think the case for callable in url dispatch is much stronger than for the others because there's still an interface to comply with in the other cases-- pluggability isn't staring us in the face quite so directly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
