Le vendredi 9 septembre 2016 07:31:42 UTC+2, Ivan Sagalaev a écrit : > I think the best end result would be one where LOGGING simply defines the >> full config and it is always applied (by Django) exactly once, and the >> defaults we want are set as the global default for LOGGING, and just >> documented so that people who want to set LOGGING themselves can easily >> copy them as a starting point. >> > > I'm actually for that, too. And the defaults should live in > global_settings.py, not hard-coded in utils/log.py > > Funny, it was exactly like that before it's been changed to the current > way in 1.5 :-) >
As the committer of the current implementation, I must admit I was probably not aware of the weird behavior of disable_existing_loggers at the time. The main drawback of the proposed solution is that each time we change the default LOGGING config, people with custom LOGGING will have to look at a diff of the change and manually merge the interesting parts in their custom config (hoping that they are reading the full release notes!). But I'm not sure there's a better solution. Claude -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/97641cbe-77c7-4aa7-b1df-22ce79ba5c62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
