Delgan

Apologies. I used an online interpreter that claims to be on version 3.5.2 but visibly is not.

Thanks for your input, @TurtleOrangina. I understand and regret that this complicates contributing to Loguru. In my view, it was a necessary trade-off to maximize accessibility for users. Now, at...

Thanks for the offer, @TurtleOrangina, but again I prefer to wait a bit longer before dropping these versions. I am certainly being over-cautious, but I want the changes planned for...

Hey @karlicoss, thank you for sharing your detailed thoughts. I hadn’t realized that `logger.exception()` might be ambiguous. That's a fair point. However, I don’t think passing exceptions directly to the...

> I feel like it's the whole point of .opt though! It contains a lot of parameters that define the behaviour of logging :) Yes, you are right. Poor wording...

Hey, thanks for sharing this snippet. In my opinion, it's a bit too complex to be added to the documentation as is, but I plan to update the serialization process...

Hi. I suggest to use `serialize=True`. This is the most common way of avoiding log injection attacks.

Hi @goseind. As you guessed, this error occurs because the logger is trying to write to a stream object that has been closed, which is invalid (see [`IOBase.close()`](https://docs.python.org/3/library/io.html#io.IOBase.close)). When removing...

Hi. Are you able to share a minimal reproducible example please?

Hi @HomerusJa. I can see how it could be useful to extend the behavior of `logger.catch()` with such "on success" parameters. However, the `logger.catch()` has evolved over the years into...