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 vinay.sajip
Recipients krivushinme, mp5023, rhettinger, serhiy.storchaka, vinay.sajip
Date 2017-10-13.14:20:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507904406.17.0.213398074469.issue30767@psf.upfronthosting.co.za>
In-reply-to
Content
> I've triggered it which is why I looked for the problem and offered the defensive patch.

That's why I asked for a small example which used logging as documented and demonstrated a problem. You haven't done that.

> As API writers you can NEVER assume your parameters are what you think they should be and just blindly proceed.

I think you'll find that in Python usage in general and the Python stdlib in particular, exhaustive checking of input parameters is not the norm. I'm not saying that no error checking is ever done nor that it should never be done, but your "NEVER" doesn't seem to hold up, as the stdlib contains many counterexamples.
History
Date User Action Args
2017-10-13 14:20:06vinay.sajipsetrecipients: + vinay.sajip, rhettinger, serhiy.storchaka, krivushinme, mp5023
2017-10-13 14:20:06vinay.sajipsetmessageid: <1507904406.17.0.213398074469.issue30767@psf.upfronthosting.co.za>
2017-10-13 14:20:06vinay.sajiplinkissue30767 messages
2017-10-13 14:20:06vinay.sajipcreate