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 pitrou
Recipients brian.curtin, loewis, pitrou, tim.golden
Date 2010-08-15.18:20:39
SpamBayes Score 2.2462978e-06
Marked as misclassified No
Message-id <1281896440.96.0.561943708802.issue9611@psf.upfronthosting.co.za>
In-reply-to
Content
The write() man page says:

       The number of bytes written may be less than count if, for example, there is  insufficient  space  on
       the underlying physical medium, or the RLIMIT_FSIZE resource limit is encountered (see setrlimit(2)),
       or the call was interrupted by a signal handler after having written less  than  count  bytes.   (See
       also pipe(7).)

So, we could return the number of bytes successfully written, and let the next call fail.

Another possibility is to only write 2GB-1 and let the caller retry.
Most people use buffered I/O, and the buffered layer automatically retries.
History
Date User Action Args
2010-08-15 18:20:41pitrousetrecipients: + pitrou, loewis, tim.golden, brian.curtin
2010-08-15 18:20:40pitrousetmessageid: <1281896440.96.0.561943708802.issue9611@psf.upfronthosting.co.za>
2010-08-15 18:20:39pitroulinkissue9611 messages
2010-08-15 18:20:39pitroucreate