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 grismar
Recipients Mariatta, grismar, gvanrossum, orsenthil, r.david.murray
Date 2016-10-02.12:19:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1475410797.87.0.257065443506.issue28294@psf.upfronthosting.co.za>
In-reply-to
Content
Breaking the API isn't good, but it will only break if log_message doesn't *receive* all messages, because that's what people who override it count on.

If there's some way of detecting who called log_message, you could use the appropriate log level on logging without compromising the API. But the only way I see without changing the signature of log_message is through inspect functions like getouterframes and that seems way nastier than these functions merit...
History
Date User Action Args
2016-10-02 12:19:57grismarsetrecipients: + grismar, gvanrossum, orsenthil, r.david.murray, Mariatta
2016-10-02 12:19:57grismarsetmessageid: <1475410797.87.0.257065443506.issue28294@psf.upfronthosting.co.za>
2016-10-02 12:19:57grismarlinkissue28294 messages
2016-10-02 12:19:57grismarcreate