On 26.09.2010, at 14:45, Florian Apolloner wrote: > Hi, > > On Sep 25, 1:25 pm, Jannis Leidel <jan...@leidel.info> wrote: >> Given the fact that the current implementation of the app cache does quite a >> few hoops to make it possible to implicitely import the models modules by >> iterating over INSTALLED_APPS, I'd like to propose to rather move the >> logging initialization to the app class initialization, instead of >> introducing another place of implicite importing -- to prevent having >> ambiguous locations for app specific code execution. > > I agree, the only problem I see (not having looked at the app refactor > branch yet + having no idea in which direction it is heading) is that > if the app class is allowed to import other stuff. Cause this might > easily end in models (or whatever) being imported and as a result we > can't guarantee that it would happen as early as startup.py (though if > someone imports critical stuff there we might get the same unwanted > results).
Not sure I understand the problem, the app instances are initialized by the app cache, at the same time as the proposed logging patch would import the startup modules. > Btw: Is there a wiki page describing exactly what the branch > solves currently and which direction it will be heading? Arthur wrote multiple status mails, please search the list archives. Jannis -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
