Message102950
There are two cases:
1) stdin and stdout go to a tty:
my_fgets() from Parser/myreadline.c does not handle the case
where fgets() reads some characters followed by an EOF. One
way to deal with this is to consider a sequence like 1234EOF
an empty line.
This is what the patch consider_1234EOF_empty_line.patch
does and it fixes problem 1.
[Another option would be to consider 1234EOF a line and
insert a newline.]
2) stdout is not a tty:
In this case, builtin_raw_input() uses PyFile_GetLine() to
read from stdin. I'm not sure why this is the case.
Perhaps 2) should be a separate issue. |
|
Date |
User |
Action |
Args |
2010-04-12 15:02:51 | skrah | set | recipients:
+ skrah, ncoghlan, lucaspmelo |
2010-04-12 15:02:50 | skrah | set | messageid: <1271084570.61.0.8582598394.issue6467@psf.upfronthosting.co.za> |
2010-04-12 15:02:48 | skrah | link | issue6467 messages |
2010-04-12 15:02:48 | skrah | create | |
|