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

2013-03-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset 533b4a1d2b23 by Vinay Sajip in branch '2.7': Issue #17521: Corrected non-enabling of logger following two calls to fileConfig(). http://hg.python.org/cpython/rev/533b4a1d2b23 New changeset 49d54e4d95df by Vinay Sajip in branch '3.2': Issue #17521:

[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's an

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

2013-03-22 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17521 ___ ___ Python-bugs-list mailing list

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

2013-03-22 Thread Vinay Sajip
Vinay Sajip added the comment: The logger obtained by logging.getLogger('root') is not the root logger, but a child of the root logger. Please post your configuration, ideally the smallest version which allows you to reproduce the failure. -- ___

[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.stdout,)