Author vstinner
Recipients vstinner
Date 2020-12-14.12:00:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607947233.16.0.810683660249.issue42639@roundup.psfhosted.org>
In-reply-to
Content
In Python 2.7, atexit was implemented in Python and registered itself using sys.exitfunc public attribute:
https://docs.python.org/2.7/library/sys.html#sys.exitfunc
https://docs.python.org/2.7/library/atexit.html#module-atexit

In Python 3.0, the atexit module was rewritten in C. A new private _Py_PyAtExit() function was added to set a new private global "pyexitfunc" variable: variable used by call_py_exitfuncs() called by Py_Finalize().

In Python 3.7, the global "pyexitfunc" variable was moved int _PyRuntimeState (commit 2ebc5ce42a8a9e047e790aefbf9a94811569b2b6), and then into PyInterpreterState (commit 776407fe893fd42972c7e3f71423d9d86741d07c).

In Python 3.7, the atexit module was upgrade to the multiphase initialization API (PEP 489): PyInit_atexit() uses PyModuleDef_Init().

Since Python 2.7, the atexit module has a limitation: if a second instance is created, the new instance overrides the old one, and old registered callbacks are newer called.

One option is to disallow creating a second instance: see bpo-40600 and PR 23699 for that.

Another option is to move the atexit state (callbacks) into PyInterpreterState. Two atexit module instances would modify the same list of callbacks. In this issue, I propose to investigate this option.
History
Date User Action Args
2020-12-14 12:00:33vstinnersetrecipients: + vstinner
2020-12-14 12:00:33vstinnersetmessageid: <1607947233.16.0.810683660249.issue42639@roundup.psfhosted.org>
2020-12-14 12:00:33vstinnerlinkissue42639 messages
2020-12-14 12:00:32vstinnercreate