A suggestion on obtaining a logger

[jsonvot]

In daily use, when multiple handlers have been added, if you need to specify a particular handler for logging, you often have to use filter functions and bind methods to filter out the desired handler for logging. This approach is somewhat indirect. It is hoped that, similar to the logging library which has a basicConfig interface, there could also be a way to directly create a logger via a method like getLogger(sink='{time:YYYYMMDD}.log'), allowing logs to be printed to that log file. This is roughly the idea. Do you think this would be more convenient?

[Delgan]

Hi.

Loguru is built around the concept of a single global logger (essentially a lightweight facade), with log management delegated to the handlers. Introducing support for multiple distinct loggers would represent a fundamental shift away from this design choice, which I don't think is very desirable.

However, I have planned a new method, namely logger.new(), which should enable creating loggers with their own independent handlers. Perhaps this will be useful in your situation. Can you please help me understand a concrete use case: why would you need to specify a particular logging for handler?