Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #98186
| From | Random832 <random832@fastmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Unbuffered stderr in Python 3 |
| Date | 2015-11-03 14:45 -0500 |
| Message-ID | <mailman.47.1446579961.8789.python-list@python.org> (permalink) |
| References | <mailman.30.1446570002.25765.python-list@python.org> <5638F707.90309@noaa.gov> |
George Trojan <george.trojan@noaa.gov> writes: > This does set line buffering, but does not change the behaviour: The opposite of line buffering is not no buffering, but full (i.e. block) buffering, that doesn't get flushed until it runs out of space. TextIOWrapper has its own internal buffer, and its design apparently doesn't contemplate the possibility of using it with a raw FileIO object (which may mean that the posted code isn't guaranteed to work) or disabling buffering.
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Unbuffered stderr in Python 3 Random832 <random832@fastmail.com> - 2015-11-03 14:45 -0500 Re: Unbuffered stderr in Python 3 Dave Farrance <df@see.replyto.invalid> - 2015-11-04 15:55 +0000
csiph-web