Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #80312 > unrolled thread

Re: Misunderstanding buffering - flushing isn't

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Misunderstanding buffering - flushing isn't Dave Angel <davea@davea.name> - 2014-11-05 23:11 -0500

#80312 — Re: Misunderstanding buffering - flushing isn't

Skip Montanaro <skip.montanaro@gmail.com> Wrote in message:
> On Wed, Nov 5, 2014 at 10:44 AM, Skip Montanaro
> <skip.montanaro@gmail.com> wrote:
>> I figured everything would be flushed to the respective .stdout and
>> .stderr files at the end of every request, but that appears not to be
>> the case.
> 
> I stand corrected. I added
> 
>         print ">> request finished"
> 
> to the end of do_GET (just before the flush() calls). I see that in
> the output files after the request finishes. Maybe I was just
> dreaming...
> 
> S
> 

Wild guess here. I've worked in environments where a newline would
 trigger a flush.  To check that,  try a trailing comma on the
 last print, which suppresses the newline.
-- 
DaveA

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web