Delgan

Thanks for investigating this bug and opening a PR, @jeremyk. Apologies for the delay. Actually, the `logger` was supposed to be thread-safe in such scenario. Unfortunately, there is a mistake...

Fixed by https://github.com/Delgan/loguru/commit/91e3646e8c0f1384d375bce49a5fb313dad5f7d6 Thanks again @jeremyk!

The `logger` should not be used as a way to store / access values. It mainly meant to provide context to the logged message. There is no way to access...

Hi @vavandrik. Thanks for the report and sorry for the inconvenience. Can you please give me more information about your environment? In particular, your OS, the version of Python, and...

Thanks for the additional details, @berke581. It clearly seems to be an issue with the package manager and not Loguru itself. The dependency on `win32-setctime` is defined in a very...

Hi @JingofXin. What is your OS version please?

It's a real mystery how you end up with such weird value after the timestamp. ``` >>> print("\xdc:\xee|Q\x7f?WA\xf8\x8bdC\xe9V\xbdW\x19q\x80") Ü:î|Q?WAødCéV½Wq ``` I don't think this is a bug in Loguru. Could...

Hi @balusch. Interesting feature. As of today, it's not easily achievable. What about using `logger.add("filename.log", rotation="2 days")`? This would ensure that the latest log is always accessible through `"filename.log"`, while...

Hi @LC117. Thanks for your suggestion. This sounds similar to https://github.com/Delgan/loguru/issues/173. See also related PR: https://github.com/Delgan/loguru/pull/1224. So far, my recommendations for your use case have been to let you define...

Can you please share the code that produces this warning? Loguru does not call `os.fork()`.