Author vinay.sajip
Recipients krivushinme, mp5023, serhiy.storchaka, vinay.sajip
Date 2017-10-12.07:18:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507792726.72.0.213398074469.issue30767@psf.upfronthosting.co.za>
In-reply-to
Content
This is not an issue that needs fixing; the current behaviour is by design. The documentation states about exc_info:

"There are two keyword arguments in kwargs which are inspected: exc_info which, if it does not evaluate as false, causes exception information to be added to the logging message. If an exception tuple (in the format returned by sys.exc_info()) is provided, it is used; otherwise, sys.exc_info() is called to get the exception information."

So, an individual exception instance returning false will not affect the truthiness of an exc_info tuple (if provided). I propose to close this issue as "not a bug" and reject the PR because (a) there's no issue to fix and (b) what Serhiy said.

If you still think there's an issue here, please post an example script which uses logging as documented and demonstrates a problem.
History
Date User Action Args
2017-10-12 07:18:46vinay.sajipsetrecipients: + vinay.sajip, serhiy.storchaka, krivushinme, mp5023
2017-10-12 07:18:46vinay.sajipsetmessageid: <1507792726.72.0.213398074469.issue30767@psf.upfronthosting.co.za>
2017-10-12 07:18:46vinay.sajiplinkissue30767 messages
2017-10-12 07:18:46vinay.sajipcreate