Ronald Oussoren <ronaldousso...@mac.com> added the comment: Hugh: never mind ....
There is a workaround for this issue: use socketpair(2) instead of pipe(2). I haven't thought enough about the consequences yet to have an firm opinion on implementing os.pipe using socketpair(2) on OSX. My gut feeling is that we shouldn't because pipes and sockets can have slightly different behavior, especially w.r.t. buffering. As a workaround for this issue you can at least use socket.socketpair instead of os.pipe. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7401> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
