Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!newsgate.cistron.nl!newsgate.news.xs4all.nl!194.109.133.85.MISMATCH!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Peter Otten <__peter__@web.de>
Subject: Re: idiomatic analogue of Perl's: while (<>) { ... }
Date: Thu, 01 Sep 2011 08:31:32 +0200
Organization: None
References: <20110901045650.GA3466@magic.hamla.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.646.1314858674.27778.python-list@python.org>
Lines: 62
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:12549

Sahil Tandon wrote:

> I've been tasked with converting some programs from Perl -> Python, and
> am (as will soon be obvious) new to the language.  A few archive/google
> searches were inconclusive on a consensus approach, which is OK, but I
> just wonder if there is a more Python-esque way to do the following in
> Python 2.7.1:
> 
> %%
> # unbuffer STDOUT
> sys.stdout = os.fdopen(sys.stdout.fileno(), 'w', 0)
> 
> # process input, line-by-line, and print responses after parsing input
> while 1:
>   rval = parse(raw_input())
>   if rval == None:
>     print('foo')
>   else:
>     print('bar')
> %%
> 
> This works, but while reading the documentation, I thought of using 'for
> line in fileinput.input()' in lieu of 'while 1:' construct.  This does
> not work when debugging the program on the command line -- the script
> appears to just hang no matter what is typed into STDIN.  I believe this
> is because of some internal buffering when using fileinput.  Is there a
> recommended way to disable such buffering?  Am I taking a totally wrong
> approach?
> 
> Feel free to just link me to previous discussions on the topic(s) if I
> have missed them.  Please be gentle with your cluebats. :-)

A quick look into fileinput.py reveals that it uses readlines() and slurps 
in the complete "file". I'm not sure that was a clever design decision...

Here's a partial reimplementation that should work for your use-case:

import sys
from itertools import chain

def _open_many(files):
    for file in files:
        if file == "-":
            yield sys.stdin
        else:
            with open(file) as f:
                yield f

def input(files=None, buffered=False):
    if files is None:
        files = sys.argv[1:]
    if not files:
        files = ["-"]
    files = _open_many(files)
    if not buffered:
        files = (iter(file.readline, "") for file in files)
    return chain.from_iterable(files)

for line in input():
    print line.strip().upper()