This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, beazley, gregory.p.smith
Date 2008-11-29.01:15:41
SpamBayes Score 0.014242525
Marked as misclassified No
Message-id <1227921346.14.0.642758939416.issue4428@psf.upfronthosting.co.za>
In-reply-to
Content
I do not agree. User code should not have to verify the return value of write().

When a big amount of data is passed to BufferedWriter.write,
- normal blocking streams should block until all data has been written.
(the implementation may call self.raw.write several times)
- non-blocking streams should raise BlockingIOError indicating the number of 
characters actually written.

This applies only to buffered files, of course.
History
Date User Action Args
2008-11-29 01:15:46amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, beazley, gregory.p.smith
2008-11-29 01:15:46amaury.forgeotdarcsetmessageid: <1227921346.14.0.642758939416.issue4428@psf.upfronthosting.co.za>
2008-11-29 01:15:43amaury.forgeotdarclinkissue4428 messages
2008-11-29 01:15:41amaury.forgeotdarccreate