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
Calling basicConfig on the top of the file for a library that is embedded into other projects can cause issue.
I suggest you drop it completely specifically because there are no change to it other than setting the default level to INFO.
I'm not against removing it, but since it is called but default anyway on the first invocation of warning(), error(), info() or debug() if not already called I thought it best to be explicit as it allows for easy switching between levels during development. Can you provide example output of the difference without to get a better idea of the issue?
byteskeptical
changed the title
calling basicConfig at this level for a library that should be embeded changes all dowstream logs
calling basicConfig at this level for a library that should be embedded changes all dowstream logs
Sep 22, 2022
Calling basicConfig on the top of the file for a library that is embedded into other projects can cause issue.
I suggest you drop it completely specifically because there are no change to it other than setting the default level to INFO.
sftpretty/sftpretty/__init__.py
Line 22 in ca8e241
In our case it added ":" to the start of every log line.
The text was updated successfully, but these errors were encountered: