Delgan

I just updated the documentation to provide more guidance about usage of a dynamic `format` function. See notably this new section of the troubleshooting page: [Why am I facing errors...

@sglbl Unfortunately, your `format_with_path()` is still error-prone due to the f-string. In your example, `{record['function']}` is evaluated and formatted before being passed to Loguru's handler. Then, the handler will treat...

Sorry, I don't have a timeline yet. The next release will be version 0.8.0 and will include breaking changes. I'd like to fit as many of them as I reasonably...

Thank you, once again, for your report and analysis. I have pinned this ticket until it is resolved.

Hey! Thank you very much for the PR. Sorry, once again, for the delay... I'm just wondering: don't you also need `*args` (and `**kwargs` to a lesser extent) to be...

Hi. This is because of `enqueue=True`. When this parameter is enabled, each log message need to be serialized before being sent through a [`Pipe`](https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Pipe) to the main process (where logs...

Yes, unfortunately this limitation still applies in your case, as the `enqueue=True` option is implemented generically and always routes logs through a `Pipe`, even though this isn't technically required for...

I agree with your sentiment, which is why I don't really like the proposed workarounds. Logging messages "asynchronously", in a background thread, should be an out-of-the-box feature of Loguru. And...

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...

Hi. I understand the rationale behind your suggestion, but it would involve changing `name` from a `str` to a custom type and implementing a separate, documented [format specification](https://docs.python.org/3/library/string.html#formatspec). However, I...