Jack Liu added the comment:

I know there is a workaround to set the global variables to None at last in 
Python scripts. But my app just provide a framework for my customers to run 
python scripts. That means the workaround requires my customers to update their 
python scripts. That may make them unhappy :(. First, we need to confirm if 
it's a bug of Python 3.5. If it's a bug of Python 3.5, is there a workaround in 
my code C++ side to call Python C APIs to resolve the memory leak issue? If 
it's not a bug of Python 3.5, is there any mistake in my C++ code?


Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list

Reply via email to