Last resort logger works only if no handlers are set.

NullHandler for example is used on most libraries in order to prevent setting up the logging system, but it can cause errors not to show.

Also, LastResort is set for the "Warning" level. -L<level> will give you the flexibility you need in order to debug issues.

Theoretically you can solve it by -L ignoring null handlers and setting last resort handler to the given level, but that's too magicky. I believe using basicConfig is the cleanest and most user friendly solution.

On Fri, Feb 21, 2020, 11:44 PM <jdveiga@gmail.com> wrote:

Ok... Though some kind of logging configuration, even a default one, is always present. For example, when logging.info() module method --or some one similar-- is called for the first time, it creates a basic logger with a last resort handler if none exists --at least up to my knowledge. So automatic set up, but set up indeed.

In any case... most important to me... I do not really know nothing about comprehensive logging. I made a search on web and on my books but does not find anything useful. Could you provide me any link or additional information on that matter, please?

Thank you.
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-leave@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/GLMJWTMZGOU3PKIUW756R4QS3VHOMPGX/
Code of Conduct: http://python.org/psf/codeofconduct/