[issue24550] maxint on 64 bit platforms breaks os.read

Martin Panter added the comment: Sorry in Python 3.5 the change was actually Issue 21932 (not Arg Clinic). But Victor said that change shouldn’t go into Python 2. BTW Issue 21199 is about Python 2’s file.read() method, not os.read(). -- resolution: duplicate -> wont fix superseder:

[issue24550] maxint on 64 bit platforms breaks os.read

Serhiy Storchaka added the comment: There is more specific issue for 32-bit reads in 2.7 (with patch): issue21199. I think this issue can be closed as a duplicate of two other issues. -- resolution: -> duplicate stage: -> resolved status: open -> closed

[issue24550] maxint on 64 bit platforms breaks os.read

Martin Panter added the comment: Yes 3.5 should do 64-bit reads (if you have enough memory) thanks to revision 0c57aba6b1a3 (Argument Clinic conversion): >>> os.read(0, 2**32) Traceback (most recent call last): File "", line 1, in MemoryError >>> os.read(0, 2**63) Traceback (most recent

[issue24550] maxint on 64 bit platforms breaks os.read

Serhiy Storchaka added the comment: The 32-bit size limit in multiprocessing is issue17560. AFAIK read() and write() now support 64-bit size on 64-bit systems. -- nosy: +haypo, serhiy.storchaka ___ Python tracker

[issue24550] maxint on 64 bit platforms breaks os.read

New submission from Brian Mingus: The lower range for this bug may be anything greater than 32 bit maxint. Other modules such as multiprocessing are limited passing objects of size 32 bit maxint, even on 64 bit systems, likely due to this issue. I have demonstrated this by modifying