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 serhiy.storchaka
Recipients eric.snow, ncoghlan, serhiy.storchaka, vstinner
Date 2017-03-23.10:49:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490266181.43.0.262535368372.issue29881@psf.upfronthosting.co.za>
In-reply-to
Content
My apologies Victor. It seems that the browser on my netbook shown only the part of changes and I seen only the change in array_array___reduce_ex__().

I like Nick's idea for hiding the indirection, but passing var_decl doesn't look having much sense to me. It should always be "static PyObject *".

I don't have a preference for the name, but the purpose of a new API is not just to ensure that a piece of initialization code is executed at most once, but that the object will be destroyed and the reference will be cleared after finalizing the interpreter. Seems this is different from the purpose of pthread_once().
History
Date User Action Args
2017-03-23 10:49:41serhiy.storchakasetrecipients: + serhiy.storchaka, ncoghlan, vstinner, eric.snow
2017-03-23 10:49:41serhiy.storchakasetmessageid: <1490266181.43.0.262535368372.issue29881@psf.upfronthosting.co.za>
2017-03-23 10:49:41serhiy.storchakalinkissue29881 messages
2017-03-23 10:49:41serhiy.storchakacreate