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 David.Austin, pitrou
Date 2010-08-13.15:43:11
SpamBayes Score 6.933783e-09
Marked as misclassified No
Message-id <1281714193.41.0.759680581334.issue9585@psf.upfronthosting.co.za>
In-reply-to
Content
The expression "largefile support" is a bit misleading. What it simply does is that it uses "long long" instead of "long" in order to store and compute file offsets. But, since a long is wide enough on your system to hold a off_t (both are 64 bits), it wouldn't make a difference. Your Python is already able to address files larger than 4GB, since it uses lseek() in all cases.

(so-called "largefile support" would be enabled if you compiled a 32-bit Python)

By the way, you can run:

$ ./python -m test.regrtest -v test_largefile

to check that the "large file" tests (> 2 GB) pass.
History
Date User Action Args
2010-08-13 15:43:13pitrousetrecipients: + pitrou, David.Austin
2010-08-13 15:43:13pitrousetmessageid: <1281714193.41.0.759680581334.issue9585@psf.upfronthosting.co.za>
2010-08-13 15:43:11pitroulinkissue9585 messages
2010-08-13 15:43:11pitroucreate