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). Btw: Is there a wiki page describing exactly what the branch solves currently and which direction it will be heading? Another question that came into my mind, after reading http://www.reddit.com/r/Python/comments/ddkal/django_vs_web2py_what_do_you_use_and_why/c0zmxqz (actually the whole thread, but that's the relevant post): Is there an easy and nice way to attach some extra info (eg request) to the logging info? Especially since I can't pass the request down all way to 3rd party apps; but I still want it to be logged in context of the current request (for easier debugging etc). The example in the reddit link isn't really convincing me -- especially since django doesn't put the request and other info into threadlocals. Regards, Florian -- 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.
