[issue22130] Logging fileConfig behavior does not match documentation

[Brendan Meeder]

Brendan Meeder added the comment:

Hi there,
  I appreciate the change to documentation but still find the updated wording 
misleading.  Existing loggers are not "left enabled," implying that existing 
loggers that were disabled before the call to fileConfig remain disabled after 
the call to fileConfig.  It is this point in particular that was problematic 
for our organization.

--

___
Python tracker 
<http://bugs.python.org/issue22130>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22130] Logging fileConfig behavior does not match documentation

[Brendan Meeder]

New submission from Brendan Meeder:

The 2.7.8 documentation for fileConfig says that for disable_existing_loggers:

"If specified as False, loggers which exist when this call is made are left 
alone."

This is actually not the case- they are enabled after the call to fileConfig. 
In particular, the loggers that would be disabled if 
disable_existing_loggers=True are enabled after the call, regardless of whether 
they were previously enabled/disabled.

--
components: Library (Lib)
messages: 224648
nosy: Brendan.Meeder
priority: normal
severity: normal
status: open
title: Logging fileConfig behavior does not match documentation
type: behavior
versions: Python 2.7

___
Python tracker 
<http://bugs.python.org/issue22130>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com