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 steve.dower
Recipients epaine, paul.moore, serhiy.storchaka, speleo3, steve.dower, tim.golden, zach.ware
Date 2020-07-29.21:25:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
At a glance, it looks like ENTER_PYTHON will *restore* the GIL on the current thread, but it may be coming in on a thread that's never seen the GIL before.

"The GIL" is actually the Python thread state, which is actually a per-thread data structure that's either active/locked or inactive/unlocked. If the current thread doesn't have a thread state, PyGILState_Ensure will create one, while ENTER_PYTHON will not.

So the underlying issue is probably that the callbacks are coming in from a thread that they shouldn't be, and really ought to be marshalled back into the correct event loop first.
Date User Action Args
2020-07-29 21:25:44steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, serhiy.storchaka, speleo3, epaine
2020-07-29 21:25:44steve.dowersetmessageid: <>
2020-07-29 21:25:44steve.dowerlinkissue40075 messages
2020-07-29 21:25:43steve.dowercreate