logging.getLevelName returns a number

[neves]

BPO	1008295
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 2006-09-20.13:47:09.000>
created_at = <Date 2004-08-12.21:56:31.000>
labels = ['library']
title = 'logging.getLevelName returns a number'
updated_at = <Date 2006-09-20.13:47:09.000>
user = 'https://bugs.python.org/neves'

bugs.python.org fields:

activity = <Date 2006-09-20.13:47:09.000>
actor = 'vinay.sajip'
assignee = 'vinay.sajip'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2004-08-12.21:56:31.000>
creator = 'neves'
dependencies = []
files = []
hgrepos = []
issue_num = 1008295
keywords = []
message_count = 4.0
messages = ['22056', '22057', '22058', '22059']
nosy_count = 3.0
nosy_names = ['vinay.sajip', 'neves', 'stevepole']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1008295'
versions = ['Python 2.3']

[neves]

logging.getLevelName function doc says that it returns
the "textual representation of logging level", but if
the argument is already the level name, the log level
integer is returned. It should return the argument.

The problem is that if I add my own levels, and call
LoggerInstance.log( levelName, message ), the formatter
will save the level number in the log, insted of the
desired level name.

[vsajip]

Logged In: YES
user_id=308438

This is not a bug, it's by design. Current CVS throws an
exception if raiseExceptions is set and you pass anything
other than an integer as the log level. The CVS
documentation has also been updated to clarify that the
level passed in is the integer rather than the level name.

[stevepole]

Logged In: YES
user_id=455201

I understand this is not a bug, it's by design.

It still looks like a bug, though. Please consider the
following code:

import logging

defaultLoglevel = logging.DEBUG
newLoglevel     = 'WARNING'

logging.basicConfig (level = defaultLoglevel, format =
'%(message)s')
print logging.getLevelName (logging.getLogger
().getEffectiveLevel ())
print logging.getLogger ().getEffectiveLevel ()
logging.getLogger ().setLevel (newLoglevel.upper ())
print logging.getLevelName (logging.getLogger
().getEffectiveLevel ())
print logging.getLogger ().getEffectiveLevel ()

Output:
DEBUG
10
30
WARNING

So the result basically inverts. Is that really the way it
is supposed to work ?

Or am I misunderstanding something ?

[vsajip]

Logged In: YES
user_id=308438

Yes, that's the way it's supposed to work - the map works
both ways, allowing the mapping of names to levels as well
as levels to names. This is because both types of mapping
are needed in the package, and it makes sense to reuse the
dictionary rather than have two separate dictionaries.

In your example, you are calling setLevel with a string
argument [newLoglevel.upper ()], which is incorrect.

I will clarify the setLevel() documentation to point out
that the level passed to setLevel() is an integer.