Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!transit4.readnews.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Pass data to a subprocess Date: Wed, 1 Aug 2012 14:16:52 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 24 Message-ID: References: <5017EFB0.6080608@shopzeus.com> NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1343830612 27997 64.122.56.22 (1 Aug 2012 14:16:52 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 1 Aug 2012 14:16:52 +0000 (UTC) User-Agent: slrn/pre1.0.0-18 (Linux) Xref: csiph.com comp.lang.python:26360 On 2012-08-01, Laszlo Nagy wrote: >> >> As I wrote "I found many nice things (Pipe, Manager and so on), but >> actually even >> this seems to work:" yes I did read the documentation. > Sorry, I did not want be offensive. >> >> I was just surprised that it worked better than I expected even >> without Pipes and Queues, but now I understand why.. >> >> Anyway now I would like to be able to detach subprocesses to avoid the >> nasty code reloading that I was talking about in another thread, but >> things get more tricky, because I can't use queues and pipes to >> communicate with a running process that it's noit my child, correct? >> > Yes, I think that is correct. I don't understand why detaching a child process on Linux/Unix would make IPC stop working. Can somebody explain? -- Grant Edwards grant.b.edwards Yow! My vaseline is at RUNNING... gmail.com