[issue17521] fileConfig() disables any previously-used "named" loggers, even when getLogger() is called again.

2013-03-22 Thread Bob Igo
Bob Igo added the comment: Any configuration I tried still generates the bug, but here's a pared-down config file: [loggers] keys=root [handlers] keys=screen [formatters] keys= [logger_root] level=DEBUG handlers=screen [handler_screen] level=DEBUG class=StreamHandler args=(sys.s

[issue17521] fileConfig() disables any previously-used "named" loggers, even when getLogger() is called again.

2013-03-22 Thread Bob Igo
New submission from Bob Igo: I am aware of the described behavior of fileConfig() when disable_existing_loggers is True, but what I am seeing happens whether disable_existing_loggers is True or False, and it also affects loggers obtained via future, fresh calls to getLogger(name). Here'