A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-August/121400.html below:

[Python-Dev] Raw I/O writelines() broken

[Python-Dev] Raw I/O writelines() broken [Python-Dev] Raw I/O writelines() brokenCameron Simpson cs at zip.com.au
Tue Aug 21 02:44:08 CEST 2012
On 21Aug2012 02:39, Andrea Griffini <agriff at tin.it> wrote:
| On Mon, Aug 20, 2012 at 11:42 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
| >> In the spirit of RawIO.write(), I think RawIO.writelines() could return
| >> the number of bytes written (allowing for partial writes).
| 
| When dealing with a non-blocking IO what you normally do is use number
| returned from the write call to make next call and try to write the
| remaining part.
| 
| How is this supposed to work with writelines? What is the caller supposed to do?

I'd expect writelines to include such logic within itself, personally.
-- 
Cameron Simpson <cs at zip.com.au>

Yield to temptation; It may not pass your way again.    - Robert A Heinlein
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4