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 serhiy.storchaka
Recipients Yaroslav.Halchenko, benjamin.peterson, eryksun, serhiy.storchaka
Date 2017-10-01.08:30:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506846632.8.0.213398074469.issue31651@psf.upfronthosting.co.za>
In-reply-to
Content
> On Linux, write() (and similar system calls) will transfer at most 0x7ffff000 (2,147,479,552) bytes, returning the number of bytes 
> actually transferred.  (This is true on both 32-bit and 64-bit 
> systems.)

This is platform-depending limitation. It can be be changed in future. In addition, there are other causes of writing not all data (see `man 2 write`).

> Also, it might be nice to add a note on top, that this module is for 'low level' IO interface, and that it is recommended to use regular file type for typical file operations (not io.FileIO) to avoid necessity of dealing limitations such as the one mentioned.

This is not true for the module overall. And this is already documented for io.RawIOBase:

"""
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
"""
History
Date User Action Args
2017-10-01 08:30:32serhiy.storchakasetrecipients: + serhiy.storchaka, benjamin.peterson, Yaroslav.Halchenko, eryksun
2017-10-01 08:30:32serhiy.storchakasetmessageid: <1506846632.8.0.213398074469.issue31651@psf.upfronthosting.co.za>
2017-10-01 08:30:32serhiy.storchakalinkissue31651 messages
2017-10-01 08:30:32serhiy.storchakacreate