Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #80312
| From | Dave Angel <davea@davea.name> |
|---|---|
| Subject | Re: Misunderstanding buffering - flushing isn't |
| Date | 2014-11-05 23:11 -0500 |
| Organization | news.gmane.org |
| References | <CANc-5UzkMpojwtTyY0kEAK1YiNnMmSKGgF0+VR=VsRUb_+etSQ@mail.gmail.com> <CANc-5UxvM2mKCcaumCyRRj_WuHa2_6vR=d5tykX9dmEkxsn9_w@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.15533.1415247125.18130.python-list@python.org> (permalink) |
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
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Misunderstanding buffering - flushing isn't Dave Angel <davea@davea.name> - 2014-11-05 23:11 -0500
csiph-web