Message259640
| Author |
vstinner |
| Recipients |
vstinner |
| Date |
2016年02月05日.08:44:19 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1454661860.28.0.473572264835.issue26292@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Copy of Antoine Pitrou's email (sent in 2012 ;-):
https://mail.python.org/pipermail/python-dev/2012-August/121396.html
Hello,
I was considering a FileIO.writelines() implementation based on
writev() and I noticed that the current RawIO.writelines()
implementation is broken: RawIO.write() can return a partial write but
writelines() ignores the result and happily proceeds to the next
iterator item (and None is returned at the end).
(it's probably broken with non-blocking streams too, for the same
reason)
In the spirit of RawIO.write(), I think RawIO.writelines() could return
the number of bytes written (allowing for partial writes).
Regards
Antoine.
--
Software development and contracting: http://pro.pitrou.net |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年02月05日 08:44:20 | vstinner | set | recipients:
+ vstinner |
| 2016年02月05日 08:44:20 | vstinner | set | messageid: <1454661860.28.0.473572264835.issue26292@psf.upfronthosting.co.za> |
| 2016年02月05日 08:44:20 | vstinner | link | issue26292 messages |
| 2016年02月05日 08:44:19 | vstinner | create |
|