You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The result is that it becomes hard to include Fitter v1.7.0 in other applications that might need to change logleves, use other handlers or just hide its output. In this sense, it was better to use Python's standard logging.
I am not sure what the solution could be, but right now I am forced to monkey-patch Fitter at runtime to be able to take control over its logging.
The text was updated successfully, but these errors were encountered:
sarusso
changed the title
New logging seems not to play nice with Python loggign.
New loguru logging seems not to play nice with Python logging.
Jan 7, 2024
dear @sarusso thanks for reporting this issue. indeed, I naively used loguru and I believe this is not really what I wanted. I need to look a bit more at the doc you sent and will probably roll back to previous version.
Hi,
commit 61d9845 introduced loguru, but it seems to me that right now it's just using Python root logger under the hood, as it might not be properly set up (as mentioned in https://github.com/Delgan/loguru?tab=readme-ov-file#suitable-for-scripts-and-libraries)
The result is that it becomes hard to include Fitter v1.7.0 in other applications that might need to change logleves, use other handlers or just hide its output. In this sense, it was better to use Python's standard logging.
I am not sure what the solution could be, but right now I am forced to monkey-patch Fitter at runtime to be able to take control over its logging.
The text was updated successfully, but these errors were encountered: