Richard Oudkerk added the comment: > - now that FDs are non-inheritable by default, fork locks around > subprocess and multiprocessing shouldn't be necessary anymore? What > other use cases does the fork-lock have?
CLOEXEC fds will still be inherited by forked children. > - the current implementation keeps hard-references to the functions > passed: so if one isn't careful, you can end up easily with a lot of > objects kept alive just because of those references, which can be a > problem True, but you could make the same complaint about atexit.register(). One can fairly easily create something like weakref.finalize which uses atfork but is smart about not creating hard refs. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16500> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
