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.

Author r.david.murray
Recipients docs@python, r.david.murray, vinay.sajip
Date 2014-09-18.14:26:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411050388.19.0.961403060223.issue22436@psf.upfronthosting.co.za>
In-reply-to
Content
https://docs.python.org/3/library/logging.html#logging.Logger.getEffectiveLevel

This says the logging level is returned, but it doesn't mention that what is returned is an integer, nor does it link to whatever method is needed to convert the integer return value into the symbolic name that the user has been using elsewhere in interacting with logging.  Indeed, the section that shows the mapping between names and numbers implies that the user of the library never needs to worry about the numbers unless they are creating a new level, but if they want to use getEffectiveLevel, this is not true.
History
Date User Action Args
2014-09-18 14:26:28r.david.murraysetrecipients: + r.david.murray, vinay.sajip, docs@python
2014-09-18 14:26:28r.david.murraysetmessageid: <1411050388.19.0.961403060223.issue22436@psf.upfronthosting.co.za>
2014-09-18 14:26:28r.david.murraylinkissue22436 messages
2014-09-18 14:26:27r.david.murraycreate