[issue27734] Memory leaks at Python35-32

Changes by R. David Murray : -- superseder: -> PEP 3121, 384 Refactoring ___ Python tracker ___

[issue27734] Memory leaks at Python35-32

Stefan Krah added the comment: #15787. All Python versions have these leaks, which aren't terribly important in practice. If it still bothers you, consider writing a Python C extension instead of "embedding" Python, which is what most people do anyway. -- status: open -> closed

[issue27734] Memory leaks at Python35-32

Филипп Пономарев added the comment: And one more thing. Is there python version exist without leaks? Or all of them have those leaks? thank you! -- ___ Python tracker

[issue27734] Memory leaks at Python35-32

Филипп Пономарев added the comment: I understand and totally agree, but if u're working on it, can u give me a reference to open issue, or should I use Stefan link? I should report to my сhief :) After that you can close it immideatly. -- status: closed -> open

[issue27734] Memory leaks at Python35-32

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

[issue27734] Memory leaks at Python35-32

Stefan Krah added the comment: It is a known problem that PEP 3121 and later similar PEPs address. Most C extensions leak a (usually very small) amount of memory with each call to Initialize()/Finalize(). IMO this issue can be closed. -- nosy: +skrah

[issue27734] Memory leaks at Python35-32

Филипп Пономарев added the comment: I've exported it in source.def - tstf @1 * thank you* Sorry for my english =) -- ___ Python tracker ___

[issue27734] Memory leaks at Python35-32

New submission from Филипп Пономарев: I've created Win32 app (MFC+ATL) Added includes, added \python35_d.lib runed main.cpp: int main() { int nRetCode = 0; HMODULE hModule = ::GetModuleHandle(nullptr); if (hModule != nullptr) { // initialize MFC and print and error on

[issue27734] Memory leaks at Python35-32

Филипп Пономарев added the comment: Hmm. Correct me if I'm not right. You agree that you have leaks, but you will not do anything with them until they start repeat in a loop? So I've updated problem. Thnx about nosy, idk. What I want is to use Python API without leaks in my programm. The

[issue27734] Memory leaks at Python35-32

Zachary Ware added the comment: Please don't remove yourself from the nosy list, we need your input to figure out exactly what may need to be fixed. -- nosy: +Филипп Пономарев ___ Python tracker

[issue27734] Memory leaks at Python35-32

Changes by Филипп Пономарев : -- components: +Windows -2to3 (2.x to 3.x conversion tool) nosy: +paul.moore, steve.dower, tim.golden, zach.ware -Филипп Пономарев type: -> resource usage ___ Python tracker

[issue27734] Memory leaks at Python35-32

Changes by Филипп Пономарев : -- components: 2to3 (2.x to 3.x conversion tool) nosy: Филипп Пономарев priority: normal severity: normal status: open title: Memory leaks at Python35-32 versions: Python 3.5 ___ Python tracker