summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_largefile.py
Commit message (Collapse)AuthorAgeFilesLines
* Take Tim's work on file.truncate out of 2.2.1 again.Michael W. Hudson2002-03-171-30/+15
|
* Backport Tim's work on getting file.truncate working better on Win32.Michael W. Hudson2002-03-161-15/+30
| | | | | "cvs diff | patch" managed to stick the NEWS item in the 2.2 final section! I wonder which silly man wrote patch <wink>.
* Ignore SIGXFSZ. Fixes #490453.Martin v. Löwis2001-12-111-0/+9
|
* Remove two XXX comments that have been resolved.Guido van Rossum2001-09-101-2/+0
|
* Move the global variables 'size' and 'name' to the top -- these areGuido van Rossum2001-09-101-5/+5
| | | | | "module parameters", and used in the Windows test (which crashed because size was undefined -- sigh).
* Change the criteria for skipping the test.Guido van Rossum2001-09-101-19/+22
| | | | | | | | | | | | | | | If on Windows, we require the 'largefile' resource. If not on Windows, we use a test that actually writes a byte beyond the 2BG limit -- seeking alone is not sufficient, since on some systems (e.g. Linux with glibc 2.2) the sytem call interface supports large seek offsets but not all filesystem implementations do. Note that on Windows, we do not use the write test: on Win2K, that test can take a minute trying to zero all those blocks on disk, and on Windows our code always supports large seek offsets (but again, not all filesystems do). This may mean that on Win95, or on certain other backward filesystems, test_largefile will *fail*.
* Dubious assumptions:Tim Peters2001-09-061-5/+10
| | | | | | | | | | | 1. That seeking beyond the end of a file increases the size of a file. 2. That files so extended are magically filled with null bytes. I find no support for either in the C std, and #2 in particular turns out not to be true on Win32 (you apparently see whatever trash happened to be on disk). Left #1 intact, but changed the test to check only bytes it explicitly wrote. Also fiddled the "expected" vs "got" failure reports to consistently use repr (%r) -- they weren't readable otherwise.
* Enable large file support on Win32 systems.Tim Peters2001-09-061-4/+4
| | | | | | | | | Curious: the MS docs say stati64 etc are supported even on Win95, but Win95 doesn't support a filesystem that allows partitions > 2 Gb. test_largefile: This was opening its test file in text mode. I have no idea how that worked under Win64, but it sure needs binary mode on Win98. BTW, on Win98 test_largefile runs quickly (under a second).
* Remove a debug print left in the code by Fred.Guido van Rossum2001-09-051-1/+0
|
* Use test_support.requires() to decide whether additional largefileBarry Warsaw2001-08-201-7/+8
| | | | tests should be run.
* When doing the quick test to see whether large files are supported,Guido van Rossum2001-04-101-1/+1
| | | | | | catch IOError as well as OverflowError. I found that on Tru64 Unix this was raised; probably because the OS (or libc) doesn't support large files but the architecture is 64 bits!
* Make reindent.py happy (convert everything to 4-space indents!).Fred Drake2000-10-231-10/+10
|
* Make sure the temporary file is cleaned up even when we raise TestSkipped.Fred Drake2000-10-231-21/+24
|
* Add largefile support for Linux64 and WIn64. Add test_largefile and some minorTrent Mick2000-08-111-0/+129
change to regrtest.py to allow optional running of test_largefile ('cause it's slow on Win64). This closes patches: http://sourceforge.net/patch/index.php?func=detailpatch&patch_id=100510&group_id=5470 and http://sourceforge.net/patch/index.php?func=detailpatch&patch_id=100511&group_id=5470
generated by cgit v0.12 at 2026-01-04 05:20:26 (GMT)