How does it relate to the "notifiers" Python library?

Hi.

That’s a very nice library that you made here, congrats! 👍

I don’t know if you are aware of the notifiers library which seems very similar to apprise as it provides a convenient API to send notifications to several providers.

I was wondering: is there any fundamental difference between these two libraries?

[Delgan]

@caronc Actually, because apprise uses standard logging, there is less risk of deadlock. I implemented loguru without relying on the built-in mechanisms, so both logging systems will live alongside without interfering with each others by default.

Problem may occur if user decides to interconnect the two logging systems by adding a specific InterceptHandler() for example. In such case, logs emitted from standard logging will be emitted to loguru handlers too. If additionally the user added a handler making use on the apprise notifier without filtering out logs coming from your library, then deadlock or recursion limit exhaustion will likely happen.

This is a complicated edge case I’m not sure can be properly fixed.

I think it’s indeed better to keep the two libraries separate from each other. Although I first thought of integrating a notification system directly into loguru, this is not along the lines of the Unix philosophy of “doing one thing and doing it well”. I prefer to leave this decision to the user. apprise and loguru are able to be interfaced together, this is not perfect for reasons you described, but I’m fine with that.

Again, thanks for the kind words, much appreciated! You made a fantastic job too with all the notification backends supported so far, and I see you are still adding new ones. That’s insane. 😄

[caronc]

I appreciate you sharing your opinion. I’ll add a conversion to MIT the TODO list. 🙂