Hello friends,

@vinay.sajip - the use case for this feature is actually something I come across fairly often.

In an application I have dozens and hundreds of logger instances. However, they all fall into one of several loggers.

Most of the instances are obtained through a module-wide logger = getLogger(__name__).

Now I have a feature in the application split over a couple of modules, in different namespaces:

zato.common.scheduler
zato.server.scheduler

They are independent yet related and it would be most convenient if I could list both in qualname - they really should share the logging configuration, at no point they should have separate handlers, logging formats, anything.

As an aside, regarding dict configuration - I know you made the comment in 2011 so it may not represent your current opinion but please keep in mind that logging config is something that on production is updated by administrators, i.e. whatever the latest trends in software development are, they aren't necessarily programmers.

People I work with have no problems with customizing ini-like files but Python dicts are an entirely different story, they are simply afraid of doing it - a missing apostrophe may mean a couple of hours wasted, for instance.