Message 161206 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	guibog
Recipients	docs@python, guibog
Date	2012年05月20日.13:39:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1337521178.31.0.00920557235265.issue14864@psf.upfronthosting.co.za>

Content
In the logging module documentation, nothing tells the user how to undo or reset a call to logging.disable(lvl). From reading the code (python 2.6 version) it seem the correct way to undo disable(lvl) is to call disable(0), but I think calling disable(NOTSET) would make more sense. The sentence I propose to add at the end of the paragraph about the disable() function is: To undo the effect of a call to logging.disable(lvl), call logging.disable(logging.NOTSET). (This is my first doc bug report, please feel free to tell me how to improve.)

Content

In the logging module documentation, nothing tells the user how to undo or reset a call to logging.disable(lvl). From reading the code (python 2.6 version) it seem the correct way to undo disable(lvl) is to call disable(0), but I think calling disable(NOTSET) would make more sense. The sentence I propose to add at the end of the paragraph about the disable() function is:
To undo the effect of a call to logging.disable(lvl), call logging.disable(logging.NOTSET).
(This is my first doc bug report, please feel free to tell me how to improve.)

History
Date	User	Action	Args
2012年05月20日 13:39:38	guibog	set	recipients: + guibog, docs@python
2012年05月20日 13:39:38	guibog	set	messageid: <1337521178.31.0.00920557235265.issue14864@psf.upfronthosting.co.za>
2012年05月20日 13:39:37	guibog	link	issue14864 messages
2012年05月20日 13:39:37	guibog	create

homepage