Antoine Pitrou added the comment: Le mardi 14 mai 2013 à 15:28 +0000, Jan Safranek a écrit : > libpython2.7.so is not unloaded because python extensions, e.g. > /usr/lib64/python2.7/lib-dynload/_heapq.so depend on it. And _heapq.so > was dlopenened by Python and it was not dlclosed -> glibc does not > unload it. > > It seems that Py_Finalize() does not even close opened shared objects. > Isn't it a bug?
What do you call shared objects in this context? .so files? Indeed they are not closed, because usually extension modules are not reload-safe: therefore, their basic structures are kept eternally once initialized. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17922> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
