click_log only applies to the initial module's logger. about click-log HOT 6 CLOSED

click_log will configure the logger for the initial module (where click_log.basic_config is called), but not other modules.

basic_config takes a logger and configures it. If you call it with __name__ it will only configure the logger for the CLI module. Call it with "todoman".

from click-log.

That still won't activate logging for third party libraries though (which is in many cases desirable).

from click-log.

from click-log.

Then pass the root logger instead

I had to do this for both click_log.basic_config("") as well as @click_log.simple_verbosity_option("").
I'm not sure this makes sense?

With the previous version none of this was necessary btw, which was the behaviour I was expecting. I'd prefer it to work the way it did, i.e. the logger is configured for all loggers.
If it's going to stay the way it is right now this should probably be documented, I'd expect more people to start asking this question.

from click-log.

from click-log.

The behavior didn't change in that regard. You still pass a logger to
basic_config / init, the default is the root logger.

This is not the case for simple_verbosity_option since it doesn't come with a default assigned to logger, see

Sure, which part of the docs are you referring to?

Something like adding a title/header with contents for:

• "Controlling the verbosity of your click-log using module". (Don't use this exact wording, it sucks :P)
• "Controlling the verbosity of all modules used"

from click-log.