homepage

I dont believe this is Windows specific, nor specific to the Win32 extensions. I can confirm that Python does leak with multiple Init/Terms, as I had to change the COM extensions to only initialize once (and hence never finalize). It is definitely related to the referenced patch (#101713)
This has been raised before, but there doesnt appear much enthusiasm for a fix. As far as I can tell, it would involve having Py_Finalize() correctly release _all_ memory allocated by Py_Initialize(). However, I have seen numerous people state that "one off" allocations that are not freed are not worth finding and freeing - however, if this bug wants a fix, then we must track them all down.
I further note that the problem is not only in the Python core, but in extension modules. Modules need a reliable way to be told that Python is finalizing so they can free their own "one off" allocations. Various hacks have been proposed for this (eg, rely on ref-count semantics to ensure that a special object is destroyed as the module dict is cleared) but nothing "reasonable" has been proposed.
Really not sure what I can do here. I am willing to do my bit in patching up the leaks, but would want a (fuzzy) commitment from python-dev that I wouldnt be doing it alone, and that it is seen as important.
I have updated the bug description and platform appropriately, but haven't reallocated a new person.