Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.043 X-Spam-Evidence: '*H*': 0.91; '*S*': 0.00; 'exception': 0.03; 'exit': 0.07; 'behave': 0.09; 'oserror': 0.09; 'retry': 0.09; 'subject:process': 0.09; 'exit)': 0.16; 'experiments': 0.16; 'are:': 0.20; "i've": 0.23; 'header:User-Agent:1': 0.26; 'skip:m 30': 0.26; 'quiet': 0.29; 'code': 0.31; 'towards': 0.32; 'to:addr :python-list': 0.33; 'hi,': 0.33; 'done': 0.34; 'something': 0.35; 'there': 0.35; 'url:org': 0.36; 'some': 0.38; 'to:addr:python.org': 0.39; 'content-disposition:inline': 0.60; 'remove': 0.61; 'movement': 0.62; 'different': 0.63; 'information': 0.63; 'more': 0.63; 'interrupted': 0.65; 'received:pl': 0.69; 'special': 0.73; 'received:internetdsl.tpnet.pl': 0.84 Date: Fri, 18 Jan 2013 13:04:38 +0100 From: Marcin Szewczyk To: python-list@python.org Subject: Inconsistent behaviour of methods waiting for child process MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.21 (2010-09-15) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - n26.netmark.pl X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - wodny.org X-Get-Message-Sender-Via: n26.netmark.pl: authenticated_id: wodny/from_h X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 26 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1358514450 news.xs4all.nl 6990 [2001:888:2000:d::a6]:47697 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:36996 Hi, I've done some experiments with: 1) multiprocessing.Process.join() 2) os.waitpid() 3) subprocess.Popen.wait() These three methods behave completely different when interrupted with a signal which I find disturbing. Reactions are: 1) exit with no exception or special return code 2) OSError exception 3) quiet retry (no exit) The 1) case is very impractical. Is there any movement towards standardization of those 3? Am I missing something and there is a way to get more information from Process.join()? -- Marcin Szewczyk http://wodny.org mailto:Marcin.Szewczyk@wodny.borg <- remove b / usuĊ„ b xmpp:wodny@ubuntu.pl xmpp:wodny@jabster.pl