[issue27734] Memory leaks at Python35-32

[R. David Murray]

R. David Murray added the comment:

Филипп: As Stefan said, we know there are problems with initialize/finalize, but the problems are deep and the project to correct them is ongoing.  So, this is an example of an already identified leak that we are working on, and consequently I'll close this issue.  (If you disagree with Stefan's diagnosis, please let us know with supporting info about why.)

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

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