Message9484
Logged In: YES
user_id=18139
Agreed on all points of fact. Also +1 on fixing it
by making iter(f).next() and f.readline() equivalent,
one way or another.
...The easy way: make f.__iter__() call readline()
instead of being so aggressive. (Better than nothing,
in my view.)
...The hard way (JvR's proposal): add a level of input
buffering on top of what the C runtime provides.
xreadlines() breaks user expectations precisely
because it does this *halfway*. Doing it right would
not be such a maintenance burden, I think. I'm willing
to write the patch, although others wiser in the ways
of diverse stdio implementations (<wink>) might want
to supervise.
...As it stands, iter(f) seems like a broken
optimization. Which is to say: it's not "undocumented
surprising behavior"; it's a bug.
|
|
Date |
User |
Action |
Args |
2007-08-23 13:59:33 | admin | link | issue524804 messages |
2007-08-23 13:59:33 | admin | create | |
|