-1 for removing logs. Like Vlastimil, it's helped me spot a couple of stray bugs.
What I'd actually like to see is this becoming stricter, with the end goal of errors raising when using undefined variables. For the verbosity, perhaps there's a middle ground? only log once per variable access per template context, and provide a formatter that will clean up the output? I believe in debug mode, you have access to line numbers and character positions, so the final output could look something like this: `` some_app/home.html:32:24: Undefined variable: *missing_variable* `` I'm unsure how much effort this would take, but it would definitely make the logging a lot more user + developer friendly. On 20 June 2017 at 08:48, Vlastimil Zíma <vlasti...@ziima.cz> wrote: > -1 to the removal. I was annoyed by the logging at first, but then I > started to clean individual logs. Half way through, I found several usages > of long removed variables, one unused template (as a side effect) and I > updated several views to always provide defined context variables. > > All in all, I consider the warnings very useful for a cleaning, though I > wouldn't be against an option to silence them. Which can already by > accomplished by LOGGING, can't it? > > Vlastik > > Dne neděle 26. března 2017 11:14:23 UTC+2 Melvyn Sopacua napsal(a): >> >> 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/80fafa13-ef3b-4b8c-9376- > cc63b1776cb8%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/80fafa13-ef3b-4b8c-9376-cc63b1776cb8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CALs0z1YDm5OYt%2B_spdXz4pgoA652fPg8V9kuW_sMWTV-qHyeEQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
