On Thursday 16 March 2017 12:03:07 Tim Graham wrote:
> Ticket #18773 [0] added logging of undefined template variables in
> Django 1.9 [1], however, I've seen several reports of users finding
> this logging more confusing than helpful. 

With channels hitting 2.0 and the already large stack of moving parts 
surrounding 
Django you need some basic system administration skills and programming 
experience to work with the system. And there are quite a few examples to link 
to 
from the user's list that deal with those moving parts rather then Django 
itself. It is 
*not* an application that you download, install and run.

An introduction "What you need to know before starting Django" would help a lot 
in 
this respect and explaining the noisiness of some logging belongs in there.

Because it *is* useful if you defined that variable to True in your settings, 
and it's 
working in all projects but this one. It could be there's an extra piece of 
context 
middleware that uses the same name and deletes the variable from the context. 
It 
could be there's a Mixin missing in the view hierarchy. Or a typo you don't 
notice 
anymore after plowing through 20+ included template bits.

Noisy logging is exactly what you want when debugging. It should log things 
that may 
be working as designed, especially things that are ambiguous (like undefined 
and 
false).

Another thing is that logging is the ugly duckling of Django. It's not 
mentioned much if 
at all in the tutorial. It is not mentioned at all in "How to write reusable 
apps" and it 
shows in the eco system. It's like finding a diamond when an app actually has 
logging 
implemented.

But it also means that novice users touching the LOGGING configuration are 
exceptions and I don't think Django should cater to the exceptions.

-- 
Melvyn Sopacua

-- 
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/70987480.KqXOiOpzpV%40devstation.
For more options, visit https://groups.google.com/d/optout.

Reply via email to