> have. It's not unique to Python, of course. Here's a confused MS
> article about it:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321788
>
> _Some_ of the PATHEXT-related redirection bugs did get fixed in XP,
> but not all of them. I haven't tried adding the registry entry they
>> But really I was hoping someone could explain *why* there is a
>> difference. If PATHEXT can detect that intest.py needs to be run
>> through Python why doesn't redirection work as expected? What
>> is happening to stdin/stdout in this case?
>
> Alas, only Microsoft could explain this, and AFAIK
[Alan Gauld]
> Thanks Danny, interesting link in that it shows a solution I
> didn't know about in the one-liner at the bottom of the discussion.
>
> But really I was hoping someone could explain *why* there is a
> difference. If PATHEXT can detect that intest.py needs to be run
> through Python w
>> C:\somepath> intest.py < in.txt
>>
>> There is no output!
>> In fact, I get an error:
>
> Yes, this is a Windows-specific thing. Unfortunately, Windows's
> treatment
> of shell scripts is slightly inconsistant. However, there are
> workarounds
> by making a '.CMD' file. See:
>
>http://a
> C:\somepath> intest.py < in.txt
>
> There is no output!
> In fact, I get an error:
>
> E:\PROJECTS\Python>intest.py < in.txt
> Traceback (most recent call last):
> File "E:\PROJECTS\Python\intest.py", line 2, in ?
> inp = raw_input()
> EOFError: EOF when reading a line
Hi Alan,
Yes, this
Hi gang, a strange one uncovered by a student of my
tutorial.
If you create the following example program, lets call it
intest.py:
### intest.py #
inp = raw_input()while inp != '': print
inp inp = raw_input()
###
And the following data file
Not
