HenrikB <henrik.bengts...@gmail.com> added the comment:
Thanks for taking your time on this one. I'll report back if I find out more about this kernel-specific issue. Here're my replies to the outstanding questions/comments: >> where the *child* process (`self.pid == 0`) get stuck while calling >> _dup2(c2pwrite = 4, 1) which in turn calls os.dup2(a = 4, b = 1). > > Doesn't child process get stuck while writing stdout? I'm not sure I understand; are you saying you would expect the child process to get stuck *before* reaching that line? If so, no, it's in the _dup2(c2pwrite = 4, 1) call where it (consistently) gets stuck. > But I don't think the assertion makes sense. I expect OSError rather > than RuntimeError. I only used RuntimeError here to keep it simple plus it wasn't obvious what the setup of OSError would be (I see that there is a FileNotFoundError in Python 3). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35305> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
