Albert Zeyer added the comment:

> Wouldn't it be better to expose and re-use the HEAD_LOCK and HEAD_UNLOCK 
> macros from pystate.c?

The macro-names HEAD_LOCK/HEAD_UNLOCK irritates me a bit. Protecting only the 
head would not be enough. Any tstate object could be invalidated. But actually, 
it protects any modification on the list (both in tstate_delete_common and in 
new_threadstate), as far as I see it.

But yes, it would be a good thing to export this locking functionality so other 
code can use it.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17263>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to