Gili T. added the comment: I read http://mail.python.org/pipermail/python-dev/2012-August/121460.html and I believe they are wrong.
I have personally run into these problems (each library maintaining its own CRT with separate heaps, file handles, etc) when static linking was used, but when dynamic linking is used there is only one CRT instance and therefore you only end up with one heap, set of file handles, etc. I've never seen the kind of problems you're referring to if dynamic linking is used. My guess is that someone (Python or an extension) is using static linking which is causing these problems. Is that a reasonable assumption? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17058> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
