[issue1752] logging.basicConfig misleading behaviour

[Vinay Sajip]

Vinay Sajip added the comment:

Added clarifying sentence to documentation (trunk only):

"The function does nothing if any handlers have been defined for the
root logger."

--
resolution:  -> fixed
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1752] logging.basicConfig misleading behaviour

[Guido van Rossum]

Guido van Rossum added the comment:

I recall being bitten by this too when first trying to use the logging
module.

I think the behavior is intentional, but I suppose it could be
documented better.

--
assignee:  -> vsajip
nosy: +gvanrossum, vsajip
priority:  -> low

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1752] logging.basicConfig misleading behaviour

[Max Ischenko]

New submission from Max Ischenko:

Function logging.basicConfig has a confusing and undocumented behaviour:
it does nothing if there are any handlers already present in root logger.

It could be more explicit, say, by giving a ValueError in such cases.

--
components: Library (Lib)
messages: 59437
nosy: imax
severity: normal
status: open
title: logging.basicConfig misleading behaviour
type: behavior
versions: Python 2.5

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com