Benjamin Slavin wrote: > * Logging may need to come even earlier. If you truly want to log > everything, you'll want to run that code first.
Is it really the case that we want to log everything? I believe that logging after initialization is enough. And for my example of a logging handler that uses ORM it's the only way it can work. Initialization by definition shouldn't do anything interesting for an application programmer to look for, it should either succeed or fail with an exception saying that it "can't run your program, sorry". As it stands now loading and processing of all the settings is the point that marks success of initialization. So I'm with Simon in putting logging somewhere where all the other settings get processed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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 -~----------~----~----~----~------~----~------~--~---
