Charles-François Natali added the comment: I have a couple random remarks: - 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? - 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 - also, since we're not sure about the API, and it's mostly intended to be used for the interpreter/stdlib, how about making it private for now, or at least "provisional' (I think that's the term)? - I'm also +1 on exceptions in prepare hook preventing fork, but we'll need to play a bit with actual fork hooks to see if that's a reasonable approach
---------- _______________________________________ 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
