andrew cooke <[EMAIL PROTECTED]> added the comment:
Got more important things than this to worry about, but yes, original
response not very helpful. In a perfect world this might be either
justified more clearly or addressed. OTOH, I get the impression hardly
anyone uses this package (docs were
Yap Sok Ann <[EMAIL PROTECTED]> added the comment:
I'd think that it is a rather common situation where one wants to use
use both fileConfig and module-level logger. As of now, the workaround
suggested by Andrew seems to be the only viable way to achieve that.
The alternative approach mentione
Vinay Sajip <[EMAIL PROTECTED]> added the comment:
This is not a bug - it's by design, as I explained in my reply to your
posting on comp.lang.python. In my reply, I suggested how you could
avoid problems.
--
assignee: -> vsajip
nosy: +vsajip
resolution: -> invalid
status: open -> clos
New submission from andrew cooke <[EMAIL PROTECTED]>:
I am seeing some odd behaviour with logging which would be explained
if loggers that are not defined explicitly (but which are controlled
via their ancestors) must be created after the logging system is
configured via fileConfig().
That's a b
