Nick Coghlan added the comment: I'm +1 for _Py_SET_FINALIZED with the semantics Serhiy suggests, and +0 for _Py_SET_ONCE.
My rationale for that preference is that _Py_SET_ONCE is a misnomer in the presence of * multiple Py_Initialize/Py_Finalize cycles; and/or * _Py_SETREF calls that replace the value to be finalized while _Py_SET_FINALIZED remains accurate in both cases. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29881> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
