[issue10363] Embedded python, handle (memory) leak

[Martin v. Löwis]

Martin v. Löwis <martin at v.loewis.de> added the comment:

As a policy, we will not rely on C++ destructors for cleanup. There are really two issues here: "global" locks, and module-specific locks.

The global locks can and should be released in Py_Finalize, with no API change. Antoine's patch looks good to me.

For module-level locks, PEP-3121-style module finalization should be used. Patches are welcome.

Martin: Please understand that there are *MANY* more issues with reloading Python in the same process, as a really large number of stuff doesn't get cleanup up on shutdown. Also expect that fixing these will take 10 years or more, unless somebody puts a huge effort into it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10363>
_______________________________________