STINNER Victor added the comment:
Duplicate of bpo-1635741.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Py_Finalize() doesn't clear all Python objects at exit
___
Python tracker
Nick Coghlan added the comment:
For the record, the open issues about applying 3121 and 384 to the standard
libary:
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21387
___
___
Python-bugs-list
Stefan Krah added the comment:
I've run Evgeniy's example under Valgrind and changed it to import
various C extensions. Unfortunately they all leak more or less, so
perhaps we can revisit this when (if?) the PEP 3121 and PEP 384
changes have been implemented.
--
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21387
___
___
Python-bugs-list
New submission from Evgeniy Stepanov:
Following https://docs.python.org/2/c-api/init.html#Py_Finalize, I'm
reinitializing embedded python interpreter multiple time in one process.
#include Python.h
void f() {
Py_Initialize();
PyRun_SimpleString(from time import time,ctime\n
import
Antoine Pitrou added the comment:
Thanks. It would be nice if you could try the same with Python 3.4, or the
development version.
--
nosy: +pitrou, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21387
Stefan Krah added the comment:
Are we fixing these on a case by case basis or is it hopeless (msg146615)?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21387
___
Antoine Pitrou added the comment:
I think fixing on a case by case is fine.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21387
___
___
