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 jbms
Recipients gregory.p.smith, izbyshev, jbms, vstinner
Date 2021-09-23.02:04:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632362673.08.0.875403105837.issue42969@roundup.psfhosted.org>
In-reply-to
Content
I suppose calling `Py_Initialize`, `Py_FinalizeEx`, then `Py_Initialize` again, then `Py_FinalizeEx` again in an embedding application, was already not particularly well supported, since it would leak memory.

However, with this change it also leaks threads.  That is a bit unfortunate, but I suppose it is just another form of memory leak, and the user can avoid it by ensuring there are no daemon threads (of course even previously, the presence of any daemon threads meant additional memory leaking).
History
Date User Action Args
2021-09-23 02:04:33jbmssetrecipients: + jbms, gregory.p.smith, vstinner, izbyshev
2021-09-23 02:04:33jbmssetmessageid: <1632362673.08.0.875403105837.issue42969@roundup.psfhosted.org>
2021-09-23 02:04:33jbmslinkissue42969 messages
2021-09-23 02:04:32jbmscreate