[issue33316] PyThread_release_lock always fails

Ivan Pozdeev added the comment: In all PyMUTEX_* and most PyCOND_* functions, all the underlying APIs are void. So there's no point for the functions to return anything other than as convention. A comment at the start of condvar.h says: "APIs generally return 0 on

[issue33316] PyThread_release_lock always fails

Steve Dower added the comment: Looks okay, but I wonder whether the implementation of PyMUTEX_UNLOCK should return something other than zero? What is it meant to return? -- ___ Python tracker

[issue33316] PyThread_release_lock always fails

Change by Ivan Pozdeev : -- keywords: +patch pull_requests: +6237 stage: -> patch review ___ Python tracker ___

[issue33316] PyThread_release_lock always fails

New submission from Ivan Pozdeev : In win7 x64 debug mode with thread_debug=1, every PyThread_release_lock() is accompanied with a message on stderr: Could not PyThread_release_lock() error: 0 -- components: Interpreter Core, Windows messages: 315497 nosy: