[issue40053] Document the behavior that no interplotation is applied when no *args are passed in for logging statements

2020-03-26 Thread Eric V. Smith
Eric V. Smith added the comment: Thanks for the bug report! I'll mark it "fixed". If there's more to do, let us know. -- resolution: -> fixed ___ Python tracker ___

[issue40053] Document the behavior that no interplotation is applied when no *args are passed in for logging statements

2020-03-26 Thread Nan Hua
Nan Hua added the comment: Note that this issue has already been mostly addressed by https://github.com/python/cpython/pull/19132. I think we can close this issue now. Thanks Eric, Gregory and Vinay! -- stage: needs patch -> resolved status: open -> closed

[issue40053] Document the behavior that no interplotation is applied when no *args are passed in for logging statements

2020-03-24 Thread Eric V. Smith
Eric V. Smith added the comment: I think it's important that logging has this feature for the reasons stated, so it should be documented. And hopefully it's also tested for, but I haven't looked. -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy:

[issue40053] Document the behavior that no interplotation is applied when no *args are passed in for logging statements

2020-03-24 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40053] Document the behavior that no interplotation is applied when no *args are passed in for logging statements

2020-03-24 Thread Nan Hua
New submission from Nan Hua : As I see, Python's logging module's implementation has a nice property that, when no additional args are passed in, the msg (first argument) will be directly printed. For example, logging.error('abc %s') can be handled peacefully with printing "ERROR:root:abc