On Thu, Jan 05, 2006 at 07:30:08PM +0100, Thomas Wouters wrote:
> On Wed, Jan 04, 2006 at 10:10:07AM -0800, Guido van Rossum wrote:
> > I'd say go right ahead and submit a change to SF (and then after it's
> > reviewed you can check it in yourself :-).
> http://www.python.org/sf?id=1397960
So, a
On Wed, Jan 04, 2006 at 10:10:07AM -0800, Guido van Rossum wrote:
> I'd say go right ahead and submit a change to SF (and then after it's
> reviewed you can check it in yourself :-).
http://www.python.org/sf?id=1397960
The patch comments and source should explain it all. The diff is quite big
(j
I'd say go right ahead and submit a change to SF (and then after it's
reviewed you can check it in yourself :-).
The only reason I can think of why this isn't done yet would be that
nobody thought of it.
Of course there are other ill-advised combinations, like write
followed by read for which std
Twice now, I've been bitten by the 'mixing file-iteration with readline'
issue. (Yeah, twice.. Good thing I don't write anything important in
Python ;) I've also seen a number of newbies bitten by the same thing. The
issue, for those that aren't aware, is that when mixing file-iteration and
readli
