Richard Oudkerk added the comment: > The write end of that pipe goes out of scope and has no references in the > child thread. Therefore, per my understanding, it should be garbage > collected (in the child thread). Where am I wrong about this?
The function which starts the child process by (indirectly) invoking os.fork() never gets a chance to finish in the child process, so nothing "goes out of scope". Anyway, relying on garbage collection to close resources for you is always a bit dodgy. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18120> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
