Gregory P. Smith added the comment: os.fork() is a low level system call wrapper. Anyone using it needs to deal with flushing whatever buffers their application has before forking among many many other things. There is a reason it lives in the os module.
It is already a dangerous system call to use from Python (ie: your child is likely to lock up if your parent had any threads). There really is nothing we can or should do to make it better. ---------- nosy: +gregory.p.smith resolution: -> wont fix status: open -> closed title: when forking without tty, code is run from start -> when forking, buffered output is not flushed first. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17230> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
