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 ov2k
Recipients ov2k
Date 2022-02-01.21:49:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643752148.46.0.568852350737.issue46605@roundup.psfhosted.org>
In-reply-to
Content
In some of the xx modules, a Py_mod_exec function steals a reference to the module argument when an error occurs (Py_XDECREF(m) after goto fail).  It's a bit pernicious given the modules' stated intent to be used as a template, although I'm not sure how often this has actually happened.  At the very least, I haven't noticed this outside the xx modules.

For Python <= 3.9, this affects xx_exec() in xxmodule.c and xx_modexec() in xxlimited.c.  For Python >= 3.10, this affects xx_exec() in xxmodule.c and xx_modexec() in xxlimited_35.c.
History
Date User Action Args
2022-02-01 21:49:08ov2ksetrecipients: + ov2k
2022-02-01 21:49:08ov2ksetmessageid: <1643752148.46.0.568852350737.issue46605@roundup.psfhosted.org>
2022-02-01 21:49:08ov2klinkissue46605 messages
2022-02-01 21:49:08ov2kcreate