Message132061
| Author |
davidsarah |
| Recipients |
David.Sankel, amaury.forgeotdarc, brian.curtin, christian.heimes, christoph, davidsarah, ezio.melotti, hippietrail, lemburg, mark, pitrou, santoso.wijaya, ssbarnea, terry.reedy, tim.golden, tzot, v+python, vstinner |
| Date |
2011年03月25日.00:54:35 |
| SpamBayes Score |
1.1610879e-10 |
| Marked as misclassified |
No |
| Message-id |
<1301014476.12.0.0130606260499.issue1602@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I wrote:
$ python3 -c 'import sys; sys.stdout.write("foo"); sys.stdout.buffer.write(b"bar"); sys.stdout.write("baz\n")'
barfoobaz
Hmm, the behaviour actually would differ here: the proposed implementation would print
foobaz
bar
(the "foobaz\n" is written by a call to WriteConsoleW and then the "bar" gets flushed to stdout when the process exits).
But since the naive expectation is "foobarbaz\n" and you already have to flush after each call in order to get that, I think this change in behaviour would be unlikely to affect correct applications. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年03月25日 00:54:36 | davidsarah | set | recipients:
+ davidsarah, lemburg, terry.reedy, tzot, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, mark, christoph, ezio.melotti, v+python, hippietrail, ssbarnea, brian.curtin, santoso.wijaya, David.Sankel |
| 2011年03月25日 00:54:36 | davidsarah | set | messageid: <1301014476.12.0.0130606260499.issue1602@psf.upfronthosting.co.za> |
| 2011年03月25日 00:54:35 | davidsarah | link | issue1602 messages |
| 2011年03月25日 00:54:35 | davidsarah | create |
|