Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #80280 > unrolled thread
| Started by | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| First post | 2014-11-05 11:06 -0600 |
| Last post | 2014-11-05 11:06 -0600 |
| Articles | 1 — 1 participant |
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.
Re: Misunderstanding buffering - flushing isn't Skip Montanaro <skip.montanaro@gmail.com> - 2014-11-05 11:06 -0600
| From | Skip Montanaro <skip.montanaro@gmail.com> |
|---|---|
| Date | 2014-11-05 11:06 -0600 |
| Subject | Re: Misunderstanding buffering - flushing isn't |
| Message-ID | <mailman.15507.1415207173.18130.python-list@python.org> |
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
Back to top | Article view | comp.lang.python
csiph-web