➜

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 christian.heimes
Recipients christian.heimes, miss-islington, theandrew168
Date 2021-03-21.15:34:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1616340861.49.0.264270057801.issue43577@roundup.psfhosted.org>
In-reply-to
Content 
No, there is no check for that. This kind of deadlock should never occur. The problem was an implementation bug in low-level C code that had bad interaction with the global interpreter lock. Python releases the GIL around OpenSSL calls. Callbacks have to re-acquire the GIL correctly and release it again at the end of a callback.

By the way the _msg_cb attribute is deliberately undocumented and marked as an internal property. I implemented the callback to debug some issues with TLS 1.3 and OpenSSL 1.1.1. It's neither well tested nor stable.
History
Date User Action Args
2021-03-21 15:34:21christian.heimessetrecipients: + christian.heimes, miss-islington, theandrew168
2021-03-21 15:34:21christian.heimessetmessageid: <1616340861.49.0.264270057801.issue43577@roundup.psfhosted.org>
2021-03-21 15:34:21christian.heimeslinkissue43577 messages
2021-03-21 15:34:21christian.heimescreate