> The problem is caused by the way that Django loads and indexes > applications. I haven't tried putting code in __init__.py, but it > certainly doesn't surprise me that it has caused you difficulties. > > > If this is not the > > case, where > > is the best place to do the kind of initialisation I want to? > > Well... this depends on exactly what sort of initialization do you > want to do. I'm still a little unclear on what you want to initialize, > and why this initialization needs to be done on module load, rather > than model synchronization, model definition or instance > instantiation).
Thanks Russ, I figured it out. It didn't really need to be done on module load - I was justy trying to do it as early as possible. Anyway, model definition time is fine, and when I moved the code from __init__.py to models.py, the problems went away. Best regards, Vinay Sajip --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
