Vinay Sajip added the comment:
It's not the docstring in the code, it's the actual documentation. I propose to
change it so that the documentation for disable will read:
Provides an overriding level *lvl* for all loggers which takes precedence over
the logger's own level. When the need arises
Simon Weber added the comment:
That sounds much clearer. Thanks!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19789
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset b6377ca8087a by Vinay Sajip in branch '2.7':
Issue #19789: Clarified documentation for logging.disable.
http://hg.python.org/cpython/rev/b6377ca8087a
New changeset 5c8130b85c17 by Vinay Sajip in branch '3.3':
Issue #19789: Clarified documentation
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19789
___
___
Python-bugs-list
New submission from Simon Weber:
In http://bugs.python.org/issue14864, this line was added to the
logging.disable docstring:
To undo the effect of a call to logging.disable(lvl), call
logging.disable(logging.NOTSET).
To prevent misunderstanding, I propose that this line be changed to:
