Closed henryruhs closed 1 year ago
Busylight uses loguru
for logging which handles things a little differently than logging available in the standard library. I've disabled logging by default in all the busylight packages (which is a best practice I was not aware of).
Patch release 0.25.5 on PyPI has this fix.
I think loguru is using logging under the hood. How can people re-enable logging?
I don't know if loguru uses logging under the hood, I suspect the answer is mostly no. You can re-enable logging using:
from loguru import logger
logger.enable('busylight'). # for the entire busylight package
logger.enable('busylight.lights') # just the lights
logger.enable('busylight.effects') # just the effects
logger.enable('busylight.api') # just the web API
Preamble Let me be clear up front: I love the amount of information the logging gives us.
Is your feature request related to a problem? Please describe. The "general" logging implementation does not allow consumer application to adjust the log-level and therfore matching the log-level is impossible.
Describe the solution you'd like
Additional context Chroma Feedback has it's own logger that is no longer respected. In this case the INFO should not be printed.