Vinay Sajip wrote:
> Currently, if the logging module is used with no handlers configured for a
> logger or its parents and you try to log events with that logger, a single
> message is printed to sys.stderr:
>
> No handlers could be found for logger <logger name>
>
> It has been suggested that this puts out a spurious message when, for
> whatever reason, a developer intentionally does not configure any
> handlers.
> [...]
>
> All feedback gratefully received,
How about a LoggingConfigurationWarning and using warnings.warn()?
Then what should happen with the warning (ignore, print, raise
exception) could be configured via the warning framework.
Bye,
Walter Dörwald
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4