On 5/29/07, Ahmad Alhashemi <[EMAIL PROTECTED]> wrote: > Well, it is called INSTALLED_APPS, not MODELS_OF_INSTALLED_APPS, > right? :) > > The only reason that the "models module of the application is what's > already used internally (in some places anyway) to refer to an > application" is because we don't have an application object. And > that's exactly what I'm proposing.
Point of fact: Python already exposes a module for each application, so its supposed non-existance is hardly the "only reason" it's done the way it is. It uses the models module instead, because that's where the useful information is stored. However, this is already well its way down a path that will accomplish nothing, so I'll take Jacob's advice and just step back from this one for a bit until it's clear what the real need is. -Gul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
