On Apr 18, 4:27 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > The problem is that "import all apps" is not a simple operation and has > lots of unexpected (at least until you get used to expecting the > unexpected) side-effects. Nested imports are the main cause. :-) > > The problem is that if application A imports something from application > B and application B is also in the list of INSTALLED_APPS (which it > would have to be in almost all cases), whilst the import of B is first > being done, the sys.modules entry for A will be empty (it will have a > key of "A" and a value of None) so that multiple imports don't happen.
This could perhaps be worked around by requiring that apps not import other apps at the top level in their __init__.py module... I don't expect that's likely to cause much incompatibility, but I'm sure there'd be some. > So anything run when B is imported cannot assume the all the other apps > have been fully imported. Cyclic import sequences and even bushy import > hierarchies are lots of fun (read "really painful") to handle. Indeed. > However, don't let my negative experiences scare you off. Write a > solution and then we can borrow it for loading.py. I'll certainly try to get something working -- I've been trying various hacky workarounds for my specific need, but nothing that's reliable and on time. Time to patch, then! Cheers, 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 -~----------~----~----~----~------~----~------~--~---
