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 vstinner
Recipients eric.snow, louielu, ncoghlan, serhiy.storchaka, vstinner
Date 2017-04-12.10:10:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I dislike _Py_SET_FINALIZED and _Py_SET_ONCE name.

I prefer to mention an "initialization" because it's a common pattern in programming and it is known that it only requires to be done once.

_PY_ONCEVAR_INIT() macro is unusual: it only evaluate the second parameter parameter, a C expression, if the variable is not initialized yet.

Py_SETREF() is different because it always evaluates its second argument, and in most cases, the second argument is an existing variable and not an expression.
Date User Action Args
2017-04-12 10:10:17vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, serhiy.storchaka, louielu
2017-04-12 10:10:17vstinnersetmessageid: <>
2017-04-12 10:10:17vstinnerlinkissue29881 messages
2017-04-12 10:10:17vstinnercreate