Closed vEpiphyte closed 7 years ago
Its possible that this guy could be called from a non-MainThread, or prior to another logging.basicConfig call being done.
This could result in disrupting a parent application's logging strategy.
Hey @vEpiphyte - Thanks a bunch for the PR!
I've been meaning to remove that - it was left in for debugging purposes, and you saved me the effort, so huge thanks!
Cheers!
Awesome!
Its possible that this guy could be called from a non-MainThread, or prior to another logging.basicConfig call being done.
This could result in disrupting a parent application's logging strategy.