Delgan

Thank you, finally we found an explanation for this issue! That happens because the `NetworkError()` in your message can't be deserialized using `pickle.loads()`. ```python import pickle from telegram.error import NetworkError...

Ok, this new error is actually the same problem that has been reported in #342! The `NetworkError()` is no longer contained in the `message` but in the `exception` of the...

Hey @j4l-Shvn. :) Loguru should perfectly fit your use case, because one of its properties is that there is is only one `logger` instance. You can configure it in one...

> When you say working did you mean logging to a file or just stderr? It was logging to `"Logs/sys_debug.log"` and only to this file. However, if a child process...

Hey @j4l-Shvn, did you figured out a solution?

Thanks for the answer. If you think the problem still persists, then I'll keep this ticket open for now. :+1:

I'm not sure to follow what is wrong with #59, is there a problem with the Pytest workaround provided? Some exceptions that are displayed while they should not? Thanks for...

> It is not really compatible from what I can tell, since exceptions are added to the message - this at least does not really work when migrating from logging...

> You could set it via private methods directly. How could I? It would require to inspect the `format` in order to detect if it contains `"{exception}"`, but I prefer...

I don't think we need coverage of the `tests/` folder. As you see, it fails the tests because of implementation details and others hacks. As long as `loguru/` actual source...