tree ca368c6b16dfa4c54fc79b9e03752182ba1b1275
parent 6e13a562ae01a962612ca76f9afcc7211240236e
author Tim Peters <tim.peters@gmail.com> 999739065 +0000
committer Tim Peters <tim.peters@gmail.com> 999739065 +0000
HG:extra convert_revision:svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/python/branches/legacy-trunk%4023000

Dubious assumptions:

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.