[issue8162] logging.disable() incoherency

Vinay Sajip added the comment: - Original Message > From: Pascal Chambon > I guess it's not important if messages > of severity 0 will allways be ignored with the current semantic > ? Levels are supposed to be positive integers, zero is a special value indicating a level that isn

[issue8162] logging.disable() incoherency

Pascal Chambon added the comment: Thanks you B-) I guess it's not important if messages of severity 0 will allways be ignored with the current semantic ? -- ___ Python tracker

[issue8162] logging.disable() incoherency

Vinay Sajip added the comment: I've updated the docstring and documentation to be more precise (r79026). -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue8162] logging.disable() incoherency

Changes by Brian Curtin : -- nosy: +vinay.sajip priority: -> normal versions: +Python 3.1, Python 3.2 ___ Python tracker ___ ___ Pytho

[issue8162] logging.disable() incoherency

New submission from Pascal Chambon : Hello I see some trouble in the semantic of logging.disable(lvl) : according to the doc (and docstrings), it's the same as a logger.setLevel(lvl) called on all logger, but in reality it doesn't act the same way : when we call logger.setLevel(lvl), log messa