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
I searched open issues and couldn't find a duplicate
What?
Rethink how we use logging in conda and conda-build.
Why?
Conda and conda-build’s logging setups are too complex. It has caused muddy logs in conda-build for years, it’s behind performance problems in conda, and floods the logs of the test suite in each run.
User impact
Application users won't suffer performance issues from excessive logging
conda-build logs will look cleaner
library users won't have to deal with the complexities built in conda's logging system
Goals
More idiomatic usage of logging, with few or no hacks.
Rethink which logging handlers are needed
Make sure the handlers are only enabled on the application layer
Document and audit which levels should be used for which kind of messages
Checklist
What?
Rethink how we use
logging
in conda and conda-build.Why?
Conda and conda-build’s logging setups are too complex. It has caused muddy logs in conda-build for years, it’s behind performance problems in conda, and floods the logs of the test suite in each run.
User impact
Goals
logging
, with few or no hacks.Tasks
log.trace(...)
#13732log.isEnabledFor(logging.DEBUG)
is always run #13541This epic is blocked by:
N/A
This epic blocks:
Not a blocker, but it does interact with #13707
The text was updated successfully, but these errors were encountered: