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 ncoghlan
Recipients ncoghlan, vinay.sajip
Date 2018-03-28.09:05:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
warnings.warn() offers a stacklevel parameter to make it easier to write helper functions that generate warnings - by passing "stacklevel=2", you can ensure the warning is attributed to the caller of the helper function, rather than to the helper function itself.

There isn't currently a similarly clear way to write helper functions that emit logging messages - if the format includes "pathname", "filename", "module", "function", or "lineno", then those will always report the location of the helper function, rather than the caller of the helper function.

It would be convenient if logging.debug() et al accepted a "stacklevel" parameter the same way the warnings module does (although this may require some adjustments to the Logger.findCaller method API)
Date User Action Args
2018-03-28 09:05:21ncoghlansetrecipients: + ncoghlan, vinay.sajip
2018-03-28 09:05:21ncoghlansetmessageid: <>
2018-03-28 09:05:21ncoghlanlinkissue33165 messages
2018-03-28 09:05:21ncoghlancreate