Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!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.014 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'subject:not': 0.03; "subject:' ": 0.07; 'happen?': 0.09; 'cc:addr:python-list': 0.11; '155': 0.16; 'from:addr:cs': 0.16; 'from:addr:zip.com.au': 0.16; 'from:name:cameron simpson': 0.16; 'message-id:@cskk.homeip.net': 0.16; 'quoted': 0.16; 'received:211.29': 0.16; 'received:211.29.132': 0.16; 'received:optusnet.com.au': 0.16; 'received:syd.optusnet.com.au': 0.16; 'simpson': 0.16; 'statement.': 0.16; 'wrote:': 0.18; '(but': 0.19; 'things.': 0.19; 'cc:addr:python.org': 0.22; 'header:User-Agent:1': 0.23; 'error': 0.23; 'cheers,': 0.24; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'fixed': 0.29; 'unix': 0.29; "doesn't": 0.30; 'especially': 0.30; 'code': 0.31; 'that.': 0.31; 'usually': 0.31; 'pipe': 0.31; 'probably': 0.32; 'subject:with': 0.35; "can't": 0.35; 'but': 0.35; 'there': 0.35; 'disk': 0.36; 'ram': 0.36; 'received:com.au': 0.36; 'charset:us- ascii': 0.36; 'should': 0.36; 'example,': 0.37; 'list': 0.37; 'implement': 0.38; 'received:211': 0.38; 'files': 0.38; 'anything': 0.39; 'even': 0.60; 'easy': 0.60; 'length': 0.61; 'content-disposition:inline': 0.62; 'real': 0.63; 'thomas': 0.65; 'grow': 0.77; 'rachel': 0.84; 'amongst': 0.91; 'carlos': 0.91; 'notion': 0.91; 'subject:True': 0.91 Date: Thu, 30 May 2013 08:18:30 +1000 From: Cameron Simpson To: Thomas Rachel Subject: Re: Piping processes works with 'shell = True' but not otherwise. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) References: X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.0 cv=BPvrNysG c=1 sm=1 a=wom5GMh1gUkA:10 a=HgrmcWlGcgYA:10 a=kj9zAlcOel0A:10 a=vrnE16BAAAAA:8 a=ZtCCktOnAAAA:8 a=Ev4b8aR72C0A:10 a=rDtMSSWv1ZI6i-tQQ_YA:9 a=CjuIK1q_8ugA:10 a=ChdAjXE5lkUvdteQbhpnkQ==:117 Cc: python-list@python.org 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: 23 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1369867287 news.xs4all.nl 15976 [2001:888:2000:d::a6]:49856 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:46419 On 29May2013 19:39, Thomas Rachel wrote: | Am 27.05.2013 02:14 schrieb Carlos Nepomuceno: | >pipes usually consumes disk storage at '/tmp'. | | Good that my pipes don't know about that. | Why should that happen? It probably doesn't on anything modern. On V7 UNIX at least there was a kernel notion of the "pipe fs", where pipe storage existed; usually /tmp; using small real (but unnamed) files is an easy way to implement them, especially on systems where RAM is very small and without a paging VM - for example, V7 UNIX ran on PDP-11s amongst other things. And files need a filesystem. But even then pipes are still small fixed length buffers; they don't grow without bound as you might have inferred from the quoted statement. Cheers, -- Cameron Simpson ERROR 155 - You can't do that. - Data General S200 Fortran error code list