Author gregory.p.smith
Recipients cagney, ebizzinfotech, gregory.p.smith, hugh, lukasz.langa, ned.deily
Date 2019-04-10.19:08:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554923327.05.0.656037376529.issue36533@roundup.psfhosted.org>
In-reply-to
Content
The problem i am fixing is merely making Python's logging library not the source of this deadlock because it was not the source in the past.  I am solving a regression in CPython behavior between 3.7.0 and 3.7.1 that led to a logging.Handler lock related deadlock in two identified problematic applications.

Breaking the logging.Handler owned locks does solve that unless someone has concrete proof from these specific applications that it does otherwise.

It would be helpful if someone *willing to actually be constructive* would test them with my PR's patch applied to their 3.7.3 interpreter as confirmation.
History
Date User Action Args
2019-04-10 19:08:47gregory.p.smithsetrecipients: + gregory.p.smith, ned.deily, lukasz.langa, cagney, hugh, ebizzinfotech
2019-04-10 19:08:47gregory.p.smithsetmessageid: <1554923327.05.0.656037376529.issue36533@roundup.psfhosted.org>
2019-04-10 19:08:47gregory.p.smithlinkissue36533 messages
2019-04-10 19:08:46gregory.p.smithcreate