Ronald Oussoren added the comment: I don't think it is possible to fix this crash other than by removing the use of _scproxy (proxy autodection on OSX) completely.
Problem is that Apple's higher level APIs (such as those used in _scproxy) don't take the use-case of calling fork(2), but not exec(2), to create child processes into account. BTW. I'm against removing _scproxy because that makes platform integration worse. I guess this should be documented somewhere, and possibly just in the documentation for os.fork() with a warning about not using just fork on OSX when there's any chance that some C extension you use calls into a higher level API. BTW. I could reproduce the crash on 10.9, but failed to do so on 10.10 earlier today (but that might just mean I have to try harder...) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20585> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
