PyMutex re-entrancy not documented, confusing existing doc

Documentation

The doc for PyMutex is very unclear if the mutex is re-entrant. Can PyMutex_Lock be called multiple times in the same thread? Do there have to be an equal number of PyMutex_Unlock calls?

The PyMutex_Lock doc says it will succeed if the thread already has the lock. PyMutex_Unlock makes no mention of it having to be called in the same thread, or if any thread is okay.

Elsewhere it says the mutex is one byte, which is not enough to do any form of counting.

The relevance is that I have C code wrapping a library and that library can make callbacks. That means there are multiple paths through the call stack. A re-entrant counting mutex would work perfectly, and it is impossible to use a non-counted lock in that scenario, short of implementing another layer of locking to do the counting.

Linked PRs

• gh-146543

Commencez par la référence de l’API PyMutex dans la documentation sur la synchronisation en C et examinez la PR liée gh-146543. Déterminez le comportement documenté pour les appels répétés à PyMutex_Lock, ainsi que le thread et le nombre d’appels requis pour PyMutex_Unlock, puis mettez à jour la documentation afin que ces règles y soient explicites.