Problems using logging module with logging.basicConfig(level=logging.NOTSET)

[panhudie]

BPO	2287
Nosy	@vsajip

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/vsajip'
closed_at = <Date 2008-03-16.21:41:01.679>
created_at = <Date 2008-03-14.13:57:06.956>
labels = ['type-bug', 'library']
title = 'Problems using logging module with logging.basicConfig(level=logging.NOTSET)'
updated_at = <Date 2008-03-16.21:41:01.672>
user = 'https://bugs.python.org/panhudie'

bugs.python.org fields:

activity = <Date 2008-03-16.21:41:01.672>
actor = 'vinay.sajip'
assignee = 'vinay.sajip'
closed = True
closed_date = <Date 2008-03-16.21:41:01.679>
closer = 'vinay.sajip'
components = ['Library (Lib)']
creation = <Date 2008-03-14.13:57:06.956>
creator = 'panhudie'
dependencies = []
files = []
hgrepos = []
issue_num = 2287
keywords = []
message_count = 2.0
messages = ['63527', '63602']
nosy_count = 2.0
nosy_names = ['vinay.sajip', 'panhudie']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2287'
versions = ['Python 2.5']

[panhudie]

The problem is in the logging.basicConfig(**kwargs):

<...>
level = kwargs.get("level")
if level:
    root.setLevel(level)

So you can not set the level like this, this logger will log WARNING(and
above) instead of all the level:

     logging.basicConfig(level=logging.NOTSET)
     #logging.NOTSET == 0, root default level is WARNING

I have seen this problem was fixed in the trunk, but not in python25 branch:

    level = kwargs.get("level")
    if level is not None:
        root.setLevel(level)

[vsajip]

Updated release25-maint.