[issue4872] Python will not co-exist with MFC (memory leak)

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

- The "memory leaks" are reported in the IDE output window when the process exits; this lists all non deallocated blocks of memory.  This feature is not enabled by default.  Creating a CString probably initializes this feature.

- Py_Finalize() doesn't free all memory used by Py_Initialize(); this is not a problem, as long as a second call to Py_Initialize() reuses the same memory.

Closing as "won't fix": there is no need to free everything when the process exits.

----------
nosy: +amaury.forgeotdarc
resolution: invalid -> wont fix
status: pending -> closed

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