On Apr 4, 12:26 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > I cannot think of any reliable way to solve this. It's a reasonably hard > problem to solve correctly, apparently. I say this because we currently > are *not* solving it in django/db/models/loading.py when we try to > initialise a cache of all apps and models. The difficulty is nested > imports and telling when a module has been fully imported. Our current > solution works most of the time, but that just makes the occasional > problem case that much more intrusive.
As it turns out, my "solution" described above fails when deployed and not using runserver -- as the signal from the first request is sent before my app has had a chance to hook it. But back to the problem -- would it not be possible for django to import all installed apps (the __init__.py, and subsequently (if present) models.py) during its own setup, and make sure they're cached (e.g. in sys.modules)*? Any app could then do independent initialisation in its __init__.py module. Django could then send out a signal to indicate that it's finished loading apps & models, and anything interested could respond to that (having hooked it in __init__.py). Could this be a workable approach, do you think? [*] Using __init__.py is not at present a good solution, as it can be executed more than once during django's startup by various __import__() calls. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
