Re: django command logging levels

Thank U for help. I will check the links to get more info :-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post

Re: django command logging levels

however, if you want to incorporate logging levels, like DEBUG, INFO, WARN in your management commands and have them correspond to a verbosity level check out https://www.crccheck.com/blog/django-management-commands-and-verbosity/ -- You received this message because you are subscribed to the

Re: django command logging levels

verbosity is varying levels of output. management commands output to stdout directly, which is different from logging. I would suggest you look at the implementation of the included django management commands and s

Re: django command logging levels

But I have added a logger setting in my django settings file, then also do I have to add verbosity setting arg in my custom management command ? On Saturday, February 16, 2019 at 4:12:07 AM UTC+5:30, Dan Davis wrote: > > The common verbosity will be passed to the handler: > > class Command(BaseCo

Re: django command logging levels

The common verbosity will be passed to the handler: class Command(BaseCommand): ... def handler(**kwargs): verbosity = kwargs['verbosity'] I tried to get clever once and not have **kwargs, but Django sends that common stuff, like '--settings", and it is good for me to pay atten