Update typing for level during setup

[userlerueda]

When setting up daiquiri, daiquiri will work perfectly fine if you provide a valid string for log_level, e.g. "DEBUG", just as in the following example code:

import daiquiri

daiquiri.setup(level="DEBUG")

However, typing tools such as mypy or pylance will complain, because the typing defined is that it must conform to the level being an int.

Looking at the nested code, for logging, when setting the level it does the following check:

_nameToLevel = {
    'CRITICAL': CRITICAL,
    'FATAL': FATAL,
    'ERROR': ERROR,
    'WARN': WARNING,
    'WARNING': WARNING,
    'INFO': INFO,
    'DEBUG': DEBUG,
    'NOTSET': NOTSET,
}

def _checkLevel(level):
    if isinstance(level, int):
        rv = level
    elif str(level) == level:
        if level not in _nameToLevel:
            raise ValueError("Unknown level: %r" % level)
        rv = _nameToLevel[level]
    else:
        raise TypeError("Level not an integer or a valid string: %r"
                        % (level,))
    return rv

So in essence it does check that it is an int or a string that is a key in the dictionary _nameToLevel.

Proposing that we update the typing so that typing checking tools do not complain.

[userlerueda]

Hi @jd it seems like although 3.2.4 is released, it is not showing up in PyPi, do you know why that is?

[jd]

Fixed