Re: os.pipe() + os.fork()

In article <256926de-e175-4fa2-aa24-dbd5f9675...@u20g2000yqu.googlegroups.com>, sebastian.no...@googlemail.com wrote: >On Feb 20, 8:13=A0pm, Gary Herron wrote: >> >> Here's a thought: =A0Consider the subprocess module. =A0 It can do thefor= >k >> and any necessary pipes and can do so in an OS ind

Re: os.pipe() + os.fork()

On Feb 20, 8:13 pm, Gary Herron wrote: > Here's a thought:  Consider the subprocess module.   It can do thefork > and any necessary pipes and can do so in an OS independent way.   It > might make you life much easier. As far as i know the subprocess module provides only functionality for running

Re: os.pipe() + os.fork()

Sebastian Noack wrote: I have figured out that, you have to close the writing end in the child process, which is reading from the pipe. Otherwise the underlying pipe is not going to be closed when the parent process is closing its writing end. This has nothing to do with Python itself. I have tri

Re: os.pipe() + os.fork()

I have figured out that, you have to close the writing end in the child process, which is reading from the pipe. Otherwise the underlying pipe is not going to be closed when the parent process is closing its writing end. This has nothing to do with Python itself. I have tried plain C and there it i

os.pipe() + os.fork()

Hi, I have a problem using os.pipe() together with os.fork(). Usually when the writing end of the pipe is closed, the reading end gets EOF. So subsequent attempts to read data will return an empty string. But when you call os.fork() after you have created a pipe using os.pipe(), and read data from