Basically, right now, when you import ndscheduler, it installs it's own logging global handler.
If you're using ndscheduler in a context where you have existing logging infrastructure, this is extremely annoying, because it means you wind up either having to manually remove the logger after import, or you get double-logging of all log output.
Anyways, this PR just turns off the logging built-into the library. If you want logging, use logging.basicConfig() or similar.
In general, a library should never install a global logging handler on import.
Basically, right now, when you import ndscheduler, it installs it's own logging global handler.
If you're using ndscheduler in a context where you have existing logging infrastructure, this is extremely annoying, because it means you wind up either having to manually remove the logger after import, or you get double-logging of all log output.
Anyways, this PR just turns off the logging built-into the library. If you want logging, use
logging.basicConfig()
or similar.In general, a library should never install a global logging handler on import.